Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 47a3c1082b6dc3d1a954a020078356f4b6716ef79dd7fc1489f62b7283034ca0

Tx prefix hash: 145348b5a47968682d43cbad98248c41daae20ded5713faaca9d56a9d67668ff
Tx public key: df496dcd233412439503c227f182e9bf8bb5e78d24c52bdd4cd4fcd6c0487c06
Timestamp: 1581515762 Timestamp [UCT]: 2020-02-12 13:56:02 Age [y:d:h:m:s]: 04:328:10:00:00
Block: 63512 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1126857 RingCT/type: yes/0
Extra: 01df496dcd233412439503c227f182e9bf8bb5e78d24c52bdd4cd4fcd6c0487c0602110000000103d36d11000000000000000000

1 output(s) for total of 378.058661238000 dcy

stealth address amount amount idx
00: b24dbd47b8807b4ac60418c89890ca66ce2b7e2b238011c034e691366cb86b0f 378.058661238000 117076 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": 63522, "vin": [ { "gen": { "height": 63512 } } ], "vout": [ { "amount": 378058661238, "target": { "key": "b24dbd47b8807b4ac60418c89890ca66ce2b7e2b238011c034e691366cb86b0f" } } ], "extra": [ 1, 223, 73, 109, 205, 35, 52, 18, 67, 149, 3, 194, 39, 241, 130, 233, 191, 139, 181, 231, 141, 36, 197, 43, 221, 76, 212, 252, 214, 192, 72, 124, 6, 2, 17, 0, 0, 0, 1, 3, 211, 109, 17, 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