Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3ab8353039fa70a9877407bcd37f66a8f78b31a0dcf6592e99ae35615008b52a

Tx prefix hash: 11b2df65e82e6df8be56952e3797031b57929c0832c9e3469219f71fe5a90d53
Tx public key: 77ad22d75fbc9fe984daf3c6ca60f1a73b2af3b202fe8144ddceeaaf70d5caf9
Timestamp: 1733464944 Timestamp [UCT]: 2024-12-06 06:02:24 Age [y:d:h:m:s]: 00:109:03:55:18
Block: 1169083 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 77811 RingCT/type: yes/0
Extra: 0177ad22d75fbc9fe984daf3c6ca60f1a73b2af3b202fe8144ddceeaaf70d5caf90211000000021f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9b8f85f5dbb737c24622040eebf32fdb9f693d34ec65d2de6551ba821faa193c 0.600000000000 1654796 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": 1169093, "vin": [ { "gen": { "height": 1169083 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9b8f85f5dbb737c24622040eebf32fdb9f693d34ec65d2de6551ba821faa193c" } } ], "extra": [ 1, 119, 173, 34, 215, 95, 188, 159, 233, 132, 218, 243, 198, 202, 96, 241, 167, 59, 42, 243, 178, 2, 254, 129, 68, 221, 206, 234, 175, 112, 213, 202, 249, 2, 17, 0, 0, 0, 2, 31, 10, 83, 235, 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