Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 809312f0d3fe2bff9d0c0b9cf0b862f434da8bf53cf032792b031e930901ebb4

Tx prefix hash: a7ff9671ccbda95af027c6a213288364febf107616b9f4846c4517efe8980e95
Tx public key: 531c66c16c01f9fcbd734c4b42220ccc1bfb07e8ad744ceb95b46b7b76f7ceab
Timestamp: 1762282901 Timestamp [UCT]: 2025-11-04 19:01:41 Age [y:d:h:m:s]: 00:065:10:58:21
Block: 1404977 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 46873 RingCT/type: yes/0
Extra: 01531c66c16c01f9fcbd734c4b42220ccc1bfb07e8ad744ceb95b46b7b76f7ceab0211000000085dfbbe2a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c5a7a2b166da7dac28e799d668158ffb9b800719391f3e29c8c61849d9a4d9bd 0.600000000000 1893346 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": 1404987, "vin": [ { "gen": { "height": 1404977 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c5a7a2b166da7dac28e799d668158ffb9b800719391f3e29c8c61849d9a4d9bd" } } ], "extra": [ 1, 83, 28, 102, 193, 108, 1, 249, 252, 189, 115, 76, 75, 66, 34, 12, 204, 27, 251, 7, 232, 173, 116, 76, 235, 149, 180, 107, 123, 118, 247, 206, 171, 2, 17, 0, 0, 0, 8, 93, 251, 190, 42, 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