Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9b151fa3e591af7e2d8f6a4322d935f48c4144bcb7c7530195be054785b0f433

Tx prefix hash: 447daf74bc95325350f655de9c3d9cd20b2045ed35d2cb92d169110313249007
Tx public key: 24879a3c224037d969a72388eeaa6db409e36cf87fe6d5b6f190cfb34e4fce6b
Timestamp: 1741246954 Timestamp [UCT]: 2025-03-06 07:42:34 Age [y:d:h:m:s]: 00:008:04:52:46
Block: 1233245 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 5887 RingCT/type: yes/0
Extra: 0124879a3c224037d969a72388eeaa6db409e36cf87fe6d5b6f190cfb34e4fce6b0211000000011f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9f3e02cf9fd7f45e80c832e01c635b8e2cde3e8b4baec20f91894c556ff37144 0.600000000000 1720164 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": 1233255, "vin": [ { "gen": { "height": 1233245 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9f3e02cf9fd7f45e80c832e01c635b8e2cde3e8b4baec20f91894c556ff37144" } } ], "extra": [ 1, 36, 135, 154, 60, 34, 64, 55, 217, 105, 167, 35, 136, 238, 170, 109, 180, 9, 227, 108, 248, 127, 230, 213, 182, 241, 144, 207, 179, 78, 79, 206, 107, 2, 17, 0, 0, 0, 1, 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