Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7dbb266416a3436b6a2778ce41e32dcb508408f2f0e33b8254c7095316d22e51

Tx prefix hash: 1cb818cd945c81ace774cb8260ad05a2d900e455db18f253a693c7566adf5a75
Tx public key: 901b0566abf277e0922b9abc7e95b750e919a2662cb2a589df29185a36dda396
Timestamp: 1732492353 Timestamp [UCT]: 2024-11-24 23:52:33 Age [y:d:h:m:s]: 00:136:04:29:06
Block: 1161031 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 97145 RingCT/type: yes/0
Extra: 01901b0566abf277e0922b9abc7e95b750e919a2662cb2a589df29185a36dda3960211000000071f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a30326b09c2843a0edfae9945ec42dbedee693b29a4a50d9bc7ebc568f47ccb2 0.600000000000 1646682 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": 1161041, "vin": [ { "gen": { "height": 1161031 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a30326b09c2843a0edfae9945ec42dbedee693b29a4a50d9bc7ebc568f47ccb2" } } ], "extra": [ 1, 144, 27, 5, 102, 171, 242, 119, 224, 146, 43, 154, 188, 126, 149, 183, 80, 233, 25, 162, 102, 44, 178, 165, 137, 223, 41, 24, 90, 54, 221, 163, 150, 2, 17, 0, 0, 0, 7, 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