Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 42090bbfec982c9c6779588a37568a63e447e311aa4e627aee44ff7d4af89d68

Tx prefix hash: 790a5abd05612ac98a6d4ce65b6fd154b691ec8e6caccebe32b7e87faed60f7d
Tx public key: ba34bc4fcf9a6a9e10d63444021377c77cc27d36de97f942a20fcb3731d2b2c5
Timestamp: 1704418797 Timestamp [UCT]: 2024-01-05 01:39:57 Age [y:d:h:m:s]: 01:123:16:00:10
Block: 928353 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 349525 RingCT/type: yes/0
Extra: 01ba34bc4fcf9a6a9e10d63444021377c77cc27d36de97f942a20fcb3731d2b2c50211000000037a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 38436aaf23a85dc55724dd205c0772ffe5388ff39f87434e2cf5e8ff3cb2b200 0.600000000000 1386211 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": 928363, "vin": [ { "gen": { "height": 928353 } } ], "vout": [ { "amount": 600000000, "target": { "key": "38436aaf23a85dc55724dd205c0772ffe5388ff39f87434e2cf5e8ff3cb2b200" } } ], "extra": [ 1, 186, 52, 188, 79, 207, 154, 106, 158, 16, 214, 52, 68, 2, 19, 119, 199, 124, 194, 125, 54, 222, 151, 249, 66, 162, 15, 203, 55, 49, 210, 178, 197, 2, 17, 0, 0, 0, 3, 122, 156, 244, 199, 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