Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 42341be9ab0a90fb4eb9a7acca5ed875ded232795504d17fe012b6ca7f88a020

Tx prefix hash: 81c18322eac0ade7b9cf4c852ec0a5ca1a561157c7470a5484c2e0e93051c206
Tx public key: b257edf007f92a5ab6c50da11a3e61db31fac8ec7c424a327de1b77d262925d9
Timestamp: 1728250724 Timestamp [UCT]: 2024-10-06 21:38:44 Age [y:d:h:m:s]: 00:185:00:41:45
Block: 1125958 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 132029 RingCT/type: yes/0
Extra: 01b257edf007f92a5ab6c50da11a3e61db31fac8ec7c424a327de1b77d262925d902110000000691e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f1262d75306ee6b652b8855fe73a4d53294a37cd20347369df76c24f99f98806 0.600000000000 1608731 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": 1125968, "vin": [ { "gen": { "height": 1125958 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f1262d75306ee6b652b8855fe73a4d53294a37cd20347369df76c24f99f98806" } } ], "extra": [ 1, 178, 87, 237, 240, 7, 249, 42, 90, 182, 197, 13, 161, 26, 62, 97, 219, 49, 250, 200, 236, 124, 66, 74, 50, 125, 225, 183, 125, 38, 41, 37, 217, 2, 17, 0, 0, 0, 6, 145, 225, 60, 4, 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