Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4d6a4a7c40b3560f48486b49444bb9bbc02018e2df0808e05b6cd17df23ca7b2

Tx prefix hash: d36e2a9559c2fe044cfd2f3d521342bc7f3055183d17b2ca4faed4c471a3a004
Tx public key: e9bac1def1982db51dc3d66058a20f88d8a7856481407b25b5759bd66aa502ac
Timestamp: 1722678467 Timestamp [UCT]: 2024-08-03 09:47:47 Age [y:d:h:m:s]: 01:095:21:47:47
Block: 1079760 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 327026 RingCT/type: yes/0
Extra: 01e9bac1def1982db51dc3d66058a20f88d8a7856481407b25b5759bd66aa502ac02110000000691e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 64d916ce253f076aaf0671709d05908b449a1f3866bbb05e0e94fb2a8a9a818a 0.600000000000 1552857 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": 1079770, "vin": [ { "gen": { "height": 1079760 } } ], "vout": [ { "amount": 600000000, "target": { "key": "64d916ce253f076aaf0671709d05908b449a1f3866bbb05e0e94fb2a8a9a818a" } } ], "extra": [ 1, 233, 186, 193, 222, 241, 152, 45, 181, 29, 195, 214, 96, 88, 162, 15, 136, 216, 167, 133, 100, 129, 64, 123, 37, 181, 117, 155, 214, 106, 165, 2, 172, 2, 17, 0, 0, 0, 6, 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