Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9e753288cac936ccfa9710305ead86a54a31376cf3afa71670f2a3d629807826

Tx prefix hash: 91119de33c8c70c41458ca0ee26d6d64c52197d3ae4b8b171e325831f898b872
Tx public key: 51fff018900f70c9c98e97fcaa29d9c07e5fa3d1b83fa20664f4a91aceb9aa28
Timestamp: 1724171572 Timestamp [UCT]: 2024-08-20 16:32:52 Age [y:d:h:m:s]: 00:233:05:02:26
Block: 1092152 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 166533 RingCT/type: yes/0
Extra: 0151fff018900f70c9c98e97fcaa29d9c07e5fa3d1b83fa20664f4a91aceb9aa2802110000000591e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3619245b231beb2291feff1457e8f3bae1802f3d5609d1f90ca4fae47b48b119 0.600000000000 1566843 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": 1092162, "vin": [ { "gen": { "height": 1092152 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3619245b231beb2291feff1457e8f3bae1802f3d5609d1f90ca4fae47b48b119" } } ], "extra": [ 1, 81, 255, 240, 24, 144, 15, 112, 201, 201, 142, 151, 252, 170, 41, 217, 192, 126, 95, 163, 209, 184, 63, 162, 6, 100, 244, 169, 26, 206, 185, 170, 40, 2, 17, 0, 0, 0, 5, 145, 225, 60, 4, 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