Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e285c64ed77e15b9ef8488b4d690545908c3da8349784031a9bbb65624429a03

Tx prefix hash: db249f7260a076b4e7b0859029eef854c9d7a15e6b2db02c7bb5d100cc6dd9ed
Tx public key: badfd86ee9da8d4b1f6948eed7113d5850430bab858ae4374ada30f7fe99b7b2
Timestamp: 1575803185 Timestamp [UCT]: 2019-12-08 11:06:25 Age [y:d:h:m:s]: 05:021:16:30:38
Block: 23197 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1161542 RingCT/type: yes/0
Extra: 01badfd86ee9da8d4b1f6948eed7113d5850430bab858ae4374ada30f7fe99b7b202110000000cad433a0b000000000000000000

1 output(s) for total of 514.307751141000 dcy

stealth address amount amount idx
00: 109e6804dbd873f0add369cef785f21e20a66aa5e348cdb807af623a1e0ac410 514.307751141000 36892 of 0

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": 23207, "vin": [ { "gen": { "height": 23197 } } ], "vout": [ { "amount": 514307751141, "target": { "key": "109e6804dbd873f0add369cef785f21e20a66aa5e348cdb807af623a1e0ac410" } } ], "extra": [ 1, 186, 223, 216, 110, 233, 218, 141, 75, 31, 105, 72, 238, 215, 17, 61, 88, 80, 67, 11, 171, 133, 138, 228, 55, 74, 218, 48, 247, 254, 153, 183, 178, 2, 17, 0, 0, 0, 12, 173, 67, 58, 11, 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