Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 02021ef6ce8dcc3c68b8a3c589a58cd879f97d7d8a6fd1192edfc64ca2ea3f52

Tx prefix hash: 99deecf61c0d5fda3dacfb44e5cbca8e8ac84e6121294efe6b9a62c10a8c1f71
Tx public key: 783ea3b51087c36586e5bc8dfb58941aeaec3e0dcddb9c5547b132583ae0b111
Timestamp: 1718379611 Timestamp [UCT]: 2024-06-14 15:40:11 Age [y:d:h:m:s]: 00:162:16:06:16
Block: 1044128 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 116420 RingCT/type: yes/0
Extra: 01783ea3b51087c36586e5bc8dfb58941aeaec3e0dcddb9c5547b132583ae0b11102110000000c52d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 511af5d280df1edd746d920b8248298e3bd4c675b894f76f9e36631afe882954 0.600000000000 1513351 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": 1044138, "vin": [ { "gen": { "height": 1044128 } } ], "vout": [ { "amount": 600000000, "target": { "key": "511af5d280df1edd746d920b8248298e3bd4c675b894f76f9e36631afe882954" } } ], "extra": [ 1, 120, 62, 163, 181, 16, 135, 195, 101, 134, 229, 188, 141, 251, 88, 148, 26, 234, 236, 62, 13, 205, 219, 156, 85, 71, 177, 50, 88, 58, 224, 177, 17, 2, 17, 0, 0, 0, 12, 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