Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0be562fb2fbb80e051aa95a2e455d3a515dd6fb0c4c0c9393c828ac98e334368

Tx prefix hash: 4c2a1b53eae5b16048a61ee47363a4423a54dabaa2e5285e1c3f6dbf7aea111e
Tx public key: 0260bae0bb57718d2084893eeee8d8d411500dfd3d087d313abd638cbff6afd2
Timestamp: 1718065985 Timestamp [UCT]: 2024-06-11 00:33:05 Age [y:d:h:m:s]: 00:142:12:53:50
Block: 1041534 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 102018 RingCT/type: yes/0
Extra: 010260bae0bb57718d2084893eeee8d8d411500dfd3d087d313abd638cbff6afd202110000000252d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 64dea67eacf58f974fd61bd2720c1d0748bbe8686feafdfa1539af9bf63be6ff 0.600000000000 1510233 of 15

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": 1041544, "vin": [ { "gen": { "height": 1041534 } } ], "vout": [ { "amount": 600000000, "target": { "key": "64dea67eacf58f974fd61bd2720c1d0748bbe8686feafdfa1539af9bf63be6ff" } } ], "extra": [ 1, 2, 96, 186, 224, 187, 87, 113, 141, 32, 132, 137, 62, 238, 232, 216, 212, 17, 80, 13, 253, 61, 8, 125, 49, 58, 189, 99, 140, 191, 246, 175, 210, 2, 17, 0, 0, 0, 2, 82, 212, 126, 148, 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