Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: 8ee0f6776a037856cdb1bd7702f70402dff22e7105301031666d852493b21087

Tx prefix hash: f149e057190f9eb243f9bed421837c7780da5671f968ec3b415f0fca309bccbd
Tx public key: a099edc6cfdf1fa8a0d219ebc7fd721c74aeb6afdf7b561610e447be81cc89b1
Timestamp: 1694873862 Timestamp [UCT]: 2023-09-16 14:17:42 Age [y:d:h:m:s]: 01:200:09:07:41
Block: 849436 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 404297 RingCT/type: yes/0
Extra: 01a099edc6cfdf1fa8a0d219ebc7fd721c74aeb6afdf7b561610e447be81cc89b1021100000001faf35c9c000000000000000000

1 output(s) for total of 0.940732118000 dcy

stealth address amount amount idx
00: 33e2b27ba00a5ca2866a2c310dba0669edc2d0ea20a6ceeffcf18fd50acad12e 0.940732118000 1303102 of 0

Check which outputs belong to given Dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them Dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinasty-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 849446, "vin": [ { "gen": { "height": 849436 } } ], "vout": [ { "amount": 940732118, "target": { "key": "33e2b27ba00a5ca2866a2c310dba0669edc2d0ea20a6ceeffcf18fd50acad12e" } } ], "extra": [ 1, 160, 153, 237, 198, 207, 223, 31, 168, 160, 210, 25, 235, 199, 253, 114, 28, 116, 174, 182, 175, 223, 123, 86, 22, 16, 228, 71, 190, 129, 204, 137, 177, 2, 17, 0, 0, 0, 1, 250, 243, 92, 156, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8