Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3862310f1b2f1f507fc42eb7611aadcd4a834ce900933d441d9a4a39265c4164

Tx prefix hash: 69d8a027a8b75b8b309bf09a6e04fb3c3722a634bb963644f2e6dc2c493edd6e
Tx public key: 509ccbc7485b510bef66b783bcc966aa586f97f4e5a91561734fc386bf9cb364
Timestamp: 1639403532 Timestamp [UCT]: 2021-12-13 13:52:12 Age [y:d:h:m:s]: 02:347:05:27:45
Block: 394658 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 766233 RingCT/type: yes/0
Extra: 01509ccbc7485b510bef66b783bcc966aa586f97f4e5a91561734fc386bf9cb36402110000000176899486000000000000000000

1 output(s) for total of 30.222791490000 dcy

stealth address amount amount idx
00: 1da93964d604a21d5a863c0c52b0331f591bc35a11a2bdb5defe58468d8cefb9 30.222791490000 792323 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": 394668, "vin": [ { "gen": { "height": 394658 } } ], "vout": [ { "amount": 30222791490, "target": { "key": "1da93964d604a21d5a863c0c52b0331f591bc35a11a2bdb5defe58468d8cefb9" } } ], "extra": [ 1, 80, 156, 203, 199, 72, 91, 81, 11, 239, 102, 183, 131, 188, 201, 102, 170, 88, 111, 151, 244, 229, 169, 21, 97, 115, 79, 195, 134, 191, 156, 179, 100, 2, 17, 0, 0, 0, 1, 118, 137, 148, 134, 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