Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ad60071318bb6ed7afb6ddf08942d80c5105cc4dd3172ddd5d3adf48001b34cb

Tx prefix hash: de745f9f5562be2d4ae76f9abaaecdf86c97d09286de73f68001c17899da1218
Tx public key: 4a9dbc81d9c5c165a13895ce5e543d140dda6463dbd3df0738f39e162d471b85
Timestamp: 1711616872 Timestamp [UCT]: 2024-03-28 09:07:52 Age [y:d:h:m:s]: 01:079:09:25:25
Block: 988070 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 317639 RingCT/type: yes/0
Extra: 014a9dbc81d9c5c165a13895ce5e543d140dda6463dbd3df0738f39e162d471b8502110000000959dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d19d43c85e3a3c50b7e0b1b6fef862a5253a8eacbc98b7e65448b554d08e61df 0.600000000000 1448331 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": 988080, "vin": [ { "gen": { "height": 988070 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d19d43c85e3a3c50b7e0b1b6fef862a5253a8eacbc98b7e65448b554d08e61df" } } ], "extra": [ 1, 74, 157, 188, 129, 217, 197, 193, 101, 161, 56, 149, 206, 94, 84, 61, 20, 13, 218, 100, 99, 219, 211, 223, 7, 56, 243, 158, 22, 45, 71, 27, 133, 2, 17, 0, 0, 0, 9, 89, 218, 211, 245, 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