Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 743700bf4fa861cf8aee432aadcdbef54326d4e69adef1b43d24688daa33fe54

Tx prefix hash: a613773414ffd6f76848e4d4386cd64ab320dd3848d353211f60819694c1fba9
Tx public key: 1e9ea5ffb1d293df8a0d9baa59a0751bab07e0fa5079742d7251fcb2a5cb3100
Timestamp: 1747258128 Timestamp [UCT]: 2025-05-14 21:28:48 Age [y:d:h:m:s]: 00:189:10:32:41
Block: 1283014 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 133092 RingCT/type: yes/0
Extra: 011e9ea5ffb1d293df8a0d9baa59a0751bab07e0fa5079742d7251fcb2a5cb310002110000000425a35a0f000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0d5ed2bf3cbbde08f81dc910e847c99e50b8e167365702a2bf5da87b69d4362f 0.600000000000 1770429 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": 1283024, "vin": [ { "gen": { "height": 1283014 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0d5ed2bf3cbbde08f81dc910e847c99e50b8e167365702a2bf5da87b69d4362f" } } ], "extra": [ 1, 30, 158, 165, 255, 177, 210, 147, 223, 138, 13, 155, 170, 89, 160, 117, 27, 171, 7, 224, 250, 80, 121, 116, 45, 114, 81, 252, 178, 165, 203, 49, 0, 2, 17, 0, 0, 0, 4, 37, 163, 90, 15, 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