Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2a98a548a7921890da8c332b709eaf841250374f69eb8d7c653c36def219bbfd

Tx prefix hash: d7eb05cd82c74af6588e1baa06412e20a9b264d14b0cd4919b22d39894de08d9
Tx public key: 0ef07f8f0ad9466da1ab299e7f6770d5a7f970b11248f3b8585ca3d7f986d2d3
Timestamp: 1726359282 Timestamp [UCT]: 2024-09-15 00:14:42 Age [y:d:h:m:s]: 00:207:22:35:11
Block: 1110272 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 148446 RingCT/type: yes/0
Extra: 010ef07f8f0ad9466da1ab299e7f6770d5a7f970b11248f3b8585ca3d7f986d2d302110000000391e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 602f96c3db83c44e2493041dbe56faadefb41cd8345ed31fe068ef85df3662b1 0.600000000000 1588817 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": 1110282, "vin": [ { "gen": { "height": 1110272 } } ], "vout": [ { "amount": 600000000, "target": { "key": "602f96c3db83c44e2493041dbe56faadefb41cd8345ed31fe068ef85df3662b1" } } ], "extra": [ 1, 14, 240, 127, 143, 10, 217, 70, 109, 161, 171, 41, 158, 127, 103, 112, 213, 167, 249, 112, 177, 18, 72, 243, 184, 88, 92, 163, 215, 249, 134, 210, 211, 2, 17, 0, 0, 0, 3, 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