Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 56e7a95e43ca198c92f5487ed675e2ae32102909d4d9147460a3602f60746305

Tx prefix hash: 17e5fd00d087d2d202d96df62ec41d426c9e5c2c9572f0ea93878fd6c9b6d313
Tx public key: ef904d5100f97d3d8a08062dec705871058c21b370fd7fda0efef961a014770e
Timestamp: 1695558585 Timestamp [UCT]: 2023-09-24 12:29:45 Age [y:d:h:m:s]: 01:186:20:02:44
Block: 855121 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 394593 RingCT/type: yes/0
Extra: 01ef904d5100f97d3d8a08062dec705871058c21b370fd7fda0efef961a014770e021100000007e6d27f9c000000000000000000

1 output(s) for total of 0.900801703000 dcy

stealth address amount amount idx
00: e77a709b9a5b6df5c2d416e8477cda28c65ae878032ad493c4d1f3d2d648c153 0.900801703000 1309125 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": 855131, "vin": [ { "gen": { "height": 855121 } } ], "vout": [ { "amount": 900801703, "target": { "key": "e77a709b9a5b6df5c2d416e8477cda28c65ae878032ad493c4d1f3d2d648c153" } } ], "extra": [ 1, 239, 144, 77, 81, 0, 249, 125, 61, 138, 8, 6, 45, 236, 112, 88, 113, 5, 140, 33, 179, 112, 253, 127, 218, 14, 254, 249, 97, 160, 20, 119, 14, 2, 17, 0, 0, 0, 7, 230, 210, 127, 156, 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