Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a3115d52d0be944cc7095c89274d5bd90618347d4f93a04a7fc6f9143cd5053a

Tx prefix hash: d7c122fa758666e709483d1b2d43fc378f6fad502bc3c9c465ecf6d974d21e8b
Tx public key: 674bb53c85f1622e4f0a9ce9354b42836358eac627398415466fb71b822e5174
Timestamp: 1583638776 Timestamp [UCT]: 2020-03-08 03:39:36 Age [y:d:h:m:s]: 04:295:10:30:25
Block: 78478 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1105864 RingCT/type: yes/0
Extra: 01674bb53c85f1622e4f0a9ce9354b42836358eac627398415466fb71b822e51740211000000094943cd9f000000000000000000

1 output(s) for total of 337.264476747000 dcy

stealth address amount amount idx
00: 9c5cd534d2c1189b3457e4606b147c554ce1003b1fe5dc21b1dedbe0a2d5e120 337.264476747000 143938 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": 78488, "vin": [ { "gen": { "height": 78478 } } ], "vout": [ { "amount": 337264476747, "target": { "key": "9c5cd534d2c1189b3457e4606b147c554ce1003b1fe5dc21b1dedbe0a2d5e120" } } ], "extra": [ 1, 103, 75, 181, 60, 133, 241, 98, 46, 79, 10, 156, 233, 53, 75, 66, 131, 99, 88, 234, 198, 39, 57, 132, 21, 70, 111, 183, 27, 130, 46, 81, 116, 2, 17, 0, 0, 0, 9, 73, 67, 205, 159, 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