Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 23b0e07ffced31fad3b1be1cb250fe6d912489569a23b0856d1e1d0b4af6536e

Tx prefix hash: 86aa1176ad038e68ffec0e4f50c7c58131c661af5bc8243cb76525e49ee0ac76
Tx public key: 56c89033ea264acf6c1112cc988824fcc57c6a14b65aaeda88bc13c3d76df4f8
Timestamp: 1734830113 Timestamp [UCT]: 2024-12-22 01:15:13 Age [y:d:h:m:s]: 00:000:11:30:44
Block: 1180414 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 341 RingCT/type: yes/0
Extra: 0156c89033ea264acf6c1112cc988824fcc57c6a14b65aaeda88bc13c3d76df4f8021100000002007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9b51d331bfb8ad1b3f3c4eee342b68a1ab35ab96037b6a9148d7665e244594ac 0.600000000000 1666825 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": 1180424, "vin": [ { "gen": { "height": 1180414 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9b51d331bfb8ad1b3f3c4eee342b68a1ab35ab96037b6a9148d7665e244594ac" } } ], "extra": [ 1, 86, 200, 144, 51, 234, 38, 74, 207, 108, 17, 18, 204, 152, 136, 36, 252, 197, 124, 106, 20, 182, 90, 174, 218, 136, 188, 19, 195, 215, 109, 244, 248, 2, 17, 0, 0, 0, 2, 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