Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 412877732f5807283b12f8960038cd640513578cf7f8b48fde766a371656d4fb

Tx prefix hash: 53ae372eb79bb1eda754b2b12f2f52c18e695c8c3b512710f355b5d15a44b6d0
Tx public key: 6bdf63011e1dfe8f44add7b231790f2d9d470e61f90509bd54f39f9b235a7ecc
Timestamp: 1737607156 Timestamp [UCT]: 2025-01-23 04:39:16 Age [y:d:h:m:s]: 00:147:01:29:47
Block: 1203334 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 104818 RingCT/type: yes/0
Extra: 016bdf63011e1dfe8f44add7b231790f2d9d470e61f90509bd54f39f9b235a7ecc021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 909a329fa20c64e893853f285b6130ba99e11d9706e79e681e438a80c7f85703 0.600000000000 1690011 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": 1203344, "vin": [ { "gen": { "height": 1203334 } } ], "vout": [ { "amount": 600000000, "target": { "key": "909a329fa20c64e893853f285b6130ba99e11d9706e79e681e438a80c7f85703" } } ], "extra": [ 1, 107, 223, 99, 1, 30, 29, 254, 143, 68, 173, 215, 178, 49, 121, 15, 45, 157, 71, 14, 97, 249, 5, 9, 189, 84, 243, 159, 155, 35, 90, 126, 204, 2, 17, 0, 0, 0, 3, 0, 127, 151, 138, 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