Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e8d7430fe4601d0b2d89acac36931e6d3fb905ac294ec20eed38d2ed6963eb61

Tx prefix hash: ccc77f9ae3361b1046d9661dde32b79e8dc71e902a4fcdb765bdc26e884d054e
Tx public key: 18d4b3f08afc02873d141a4c16393652b3e3082df8d16f0e505e877600d5ecb4
Timestamp: 1744724851 Timestamp [UCT]: 2025-04-15 13:47:31 Age [y:d:h:m:s]: 00:005:08:52:52
Block: 1262031 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 3825 RingCT/type: yes/0
Extra: 0118d4b3f08afc02873d141a4c16393652b3e3082df8d16f0e505e877600d5ecb4021100000001e4dc9009000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1b873be8eced5ca2a9ba329a250fa7cf725b65025909ace1c15b78ab5f45ffb6 0.600000000000 1749208 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": 1262041, "vin": [ { "gen": { "height": 1262031 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1b873be8eced5ca2a9ba329a250fa7cf725b65025909ace1c15b78ab5f45ffb6" } } ], "extra": [ 1, 24, 212, 179, 240, 138, 252, 2, 135, 61, 20, 26, 76, 22, 57, 54, 82, 179, 227, 8, 45, 248, 209, 111, 14, 80, 94, 135, 118, 0, 213, 236, 180, 2, 17, 0, 0, 0, 1, 228, 220, 144, 9, 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