Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f86b1f44515cfa42adea457015cd7aa59fb0d52492c2cfefec0c30cfd2f0b207

Tx prefix hash: b5e67334df27728fee499853d726739409aa7082a8a951da3b6d04d4b4519d93
Tx public key: 0507bb59a3e672b871d3ec59137903db11960d52d296e199ed7dc1cf60aef41c
Timestamp: 1648609267 Timestamp [UCT]: 2022-03-30 03:01:07 Age [y:d:h:m:s]: 03:220:01:34:18
Block: 469305 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 935247 RingCT/type: yes/0
Extra: 010507bb59a3e672b871d3ec59137903db11960d52d296e199ed7dc1cf60aef41c0211000000085eb576c5000000000000000000

1 output(s) for total of 17.100073131000 dcy

stealth address amount amount idx
00: cffe6dcd633c1b08d1799f96dcead36e02924499535fccfe6c9a097349dcf3c5 17.100073131000 888227 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": 469315, "vin": [ { "gen": { "height": 469305 } } ], "vout": [ { "amount": 17100073131, "target": { "key": "cffe6dcd633c1b08d1799f96dcead36e02924499535fccfe6c9a097349dcf3c5" } } ], "extra": [ 1, 5, 7, 187, 89, 163, 230, 114, 184, 113, 211, 236, 89, 19, 121, 3, 219, 17, 150, 13, 82, 210, 150, 225, 153, 237, 125, 193, 207, 96, 174, 244, 28, 2, 17, 0, 0, 0, 8, 94, 181, 118, 197, 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