Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ddabb9fa36ae493915c556f647bc65fe36e65314d508e943324aee12d3e1ac6d

Tx prefix hash: 330e36d9f981588904b84f3a4530dcb9256b2d8fc083923e03806bf294ecff6d
Tx public key: a96f1a5947b714a18326b60886efa53204a700a9cd85e0e3443e86df7e00a13b
Timestamp: 1711541894 Timestamp [UCT]: 2024-03-27 12:18:14 Age [y:d:h:m:s]: 01:085:07:04:22
Block: 987460 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 321781 RingCT/type: yes/0
Extra: 01a96f1a5947b714a18326b60886efa53204a700a9cd85e0e3443e86df7e00a13b0211000000020011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5b3f161f2f8227fff61f52ccee76c0ef3440a62bcd3caecb863450c1ccb9a04e 0.600000000000 1447711 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": 987470, "vin": [ { "gen": { "height": 987460 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5b3f161f2f8227fff61f52ccee76c0ef3440a62bcd3caecb863450c1ccb9a04e" } } ], "extra": [ 1, 169, 111, 26, 89, 71, 183, 20, 161, 131, 38, 182, 8, 134, 239, 165, 50, 4, 167, 0, 169, 205, 133, 224, 227, 68, 62, 134, 223, 126, 0, 161, 59, 2, 17, 0, 0, 0, 2, 0, 17, 5, 91, 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