Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 636e921735fbf5cc2005401ff0f3ea679a174d9ca5bab9f3e3c51492f5496a12

Tx prefix hash: ea121f1f5ba21a2b57f0cf81577c277ef4567200e531fe825daf9139962a15fb
Tx public key: 6d601c9c0b9c063bafff2887059624cb15b730fa64248a859c46b125813d0d70
Timestamp: 1727979323 Timestamp [UCT]: 2024-10-03 18:15:23 Age [y:d:h:m:s]: 00:210:11:31:19
Block: 1123713 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 150237 RingCT/type: yes/0
Extra: 016d601c9c0b9c063bafff2887059624cb15b730fa64248a859c46b125813d0d7002110000000291e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f2ea8c7251852a66c931d992b8f0434b220456b8e5bdc72550a978837f8f437f 0.600000000000 1606248 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": 1123723, "vin": [ { "gen": { "height": 1123713 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f2ea8c7251852a66c931d992b8f0434b220456b8e5bdc72550a978837f8f437f" } } ], "extra": [ 1, 109, 96, 28, 156, 11, 156, 6, 59, 175, 255, 40, 135, 5, 150, 36, 203, 21, 183, 48, 250, 100, 36, 138, 133, 156, 70, 177, 37, 129, 61, 13, 112, 2, 17, 0, 0, 0, 2, 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