Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a01592c591a2f0b0e4c366090047e80733e2bf93982998ad8cf2fb8a94fe2f9d

Tx prefix hash: 49feb12cd48f06c5b806940e5e1561ced0d9ef4846c3e47fdb0656b26cd9a8d7
Tx public key: 106641fd9ae9472caeee40c6efe4557c346f569b6fa3fb496e1a5a9e58a70221
Timestamp: 1698420008 Timestamp [UCT]: 2023-10-27 15:20:08 Age [y:d:h:m:s]: 01:121:14:54:37
Block: 878867 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 347873 RingCT/type: yes/0
Extra: 01106641fd9ae9472caeee40c6efe4557c346f569b6fa3fb496e1a5a9e58a702210211000000064b8f5122000000000000000000

1 output(s) for total of 0.751534303000 dcy

stealth address amount amount idx
00: 31d14be4dffee390b60c0ce6da5b921f940d891c12804a73e94b053f07f99e38 0.751534303000 1334357 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": 878877, "vin": [ { "gen": { "height": 878867 } } ], "vout": [ { "amount": 751534303, "target": { "key": "31d14be4dffee390b60c0ce6da5b921f940d891c12804a73e94b053f07f99e38" } } ], "extra": [ 1, 16, 102, 65, 253, 154, 233, 71, 44, 174, 238, 64, 198, 239, 228, 85, 124, 52, 111, 86, 155, 111, 163, 251, 73, 110, 26, 90, 158, 88, 167, 2, 33, 2, 17, 0, 0, 0, 6, 75, 143, 81, 34, 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