Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f0f508e344c77720888eab543807bb880fa3f24480ea6b3e92793a67e8c0b398

Tx prefix hash: f301c973875965744ecfd9fddbb486a11185d9716b8f18eaef53fab9ec756419
Tx public key: 974f25a93e98a7e830f49fad6103a1e41bc0c99d477c2f8a5c22607c099c0129
Timestamp: 1749549908 Timestamp [UCT]: 2025-06-10 10:05:08 Age [y:d:h:m:s]: 00:160:06:20:46
Block: 1301990 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 112215 RingCT/type: yes/0
Extra: 01974f25a93e98a7e830f49fad6103a1e41bc0c99d477c2f8a5c22607c099c0129021100000002bf51b2a2000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8e34cefc27e17414ce25954d5a0a9c04c0f796781caa74da30ad315044bb33f6 0.600000000000 1789557 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": 1302000, "vin": [ { "gen": { "height": 1301990 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8e34cefc27e17414ce25954d5a0a9c04c0f796781caa74da30ad315044bb33f6" } } ], "extra": [ 1, 151, 79, 37, 169, 62, 152, 167, 232, 48, 244, 159, 173, 97, 3, 161, 228, 27, 192, 201, 157, 71, 124, 47, 138, 92, 34, 96, 124, 9, 156, 1, 41, 2, 17, 0, 0, 0, 2, 191, 81, 178, 162, 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