Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c0e5cb8296cdb21f649fdf899c94a5c00b12520872d886e212831011e8b6572a

Tx prefix hash: 764b5bbf6fdecf473871fe2b92c03c08a26da4b7d10b47d3dfc1a630cfd6a2e4
Tx public key: 9ce344d752ffcba11cd1715a992b8f64a7ac493662b98c4af5dd5e90057f88cb
Timestamp: 1732058677 Timestamp [UCT]: 2024-11-19 23:24:37 Age [y:d:h:m:s]: 00:004:06:12:18
Block: 1157439 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 3040 RingCT/type: yes/0
Extra: 019ce344d752ffcba11cd1715a992b8f64a7ac493662b98c4af5dd5e90057f88cb0211000000011f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 829cea75676c742d64f9a5ba050c6ca084d90aecb44b56583b2443854450b14e 0.600000000000 1643062 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": 1157449, "vin": [ { "gen": { "height": 1157439 } } ], "vout": [ { "amount": 600000000, "target": { "key": "829cea75676c742d64f9a5ba050c6ca084d90aecb44b56583b2443854450b14e" } } ], "extra": [ 1, 156, 227, 68, 215, 82, 255, 203, 161, 28, 209, 113, 90, 153, 43, 143, 100, 167, 172, 73, 54, 98, 185, 140, 74, 245, 221, 94, 144, 5, 127, 136, 203, 2, 17, 0, 0, 0, 1, 31, 10, 83, 235, 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