Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5f95ae06ec2f478cb039e957f96891543127aaea919d7706187830ca3827ea48

Tx prefix hash: 778c0e844209150d69b2d85ee40b83617b8283393c0a9cc48e5e3d98de569fac
Tx public key: 6696eac5278bde95652d2322008c507aca59c0a3e7e224fdf637fa5f9726a7aa
Timestamp: 1722420577 Timestamp [UCT]: 2024-07-31 10:09:37 Age [y:d:h:m:s]: 00:085:03:09:34
Block: 1077616 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 60949 RingCT/type: yes/0
Extra: 016696eac5278bde95652d2322008c507aca59c0a3e7e224fdf637fa5f9726a7aa02110000000d91e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 04e93ee38d4d2d9fa16a1028f0a2ea901e2c7f7f3ef1a4eabaa221667717c8c3 0.600000000000 1550171 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": 1077626, "vin": [ { "gen": { "height": 1077616 } } ], "vout": [ { "amount": 600000000, "target": { "key": "04e93ee38d4d2d9fa16a1028f0a2ea901e2c7f7f3ef1a4eabaa221667717c8c3" } } ], "extra": [ 1, 102, 150, 234, 197, 39, 139, 222, 149, 101, 45, 35, 34, 0, 140, 80, 122, 202, 89, 192, 163, 231, 226, 36, 253, 246, 55, 250, 95, 151, 38, 167, 170, 2, 17, 0, 0, 0, 13, 145, 225, 60, 4, 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