Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1ae696c405e682e07b9a88f350326a4319315339cf0c4d5ae16064fcd580a1d3

Tx prefix hash: 92df6bfdd10f66410b6b9cdabeaab4272f4116fb24809a97a92a6d9a64ccd4a8
Tx public key: 5d5557ce3fb6a88dc12894a7dd75ebac20c9e62d7919c7122be123a4c6ea9da1
Timestamp: 1726469111 Timestamp [UCT]: 2024-09-16 06:45:11 Age [y:d:h:m:s]: 01:053:22:28:02
Block: 1111180 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 296961 RingCT/type: yes/0
Extra: 015d5557ce3fb6a88dc12894a7dd75ebac20c9e62d7919c7122be123a4c6ea9da1021100000006e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 430cb895536af7e5ce11584ddadbdf8af7bad3cefcda3662298857c0fe050cb5 0.600000000000 1590051 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": 1111190, "vin": [ { "gen": { "height": 1111180 } } ], "vout": [ { "amount": 600000000, "target": { "key": "430cb895536af7e5ce11584ddadbdf8af7bad3cefcda3662298857c0fe050cb5" } } ], "extra": [ 1, 93, 85, 87, 206, 63, 182, 168, 141, 193, 40, 148, 167, 221, 117, 235, 172, 32, 201, 230, 45, 121, 25, 199, 18, 43, 225, 35, 164, 198, 234, 157, 161, 2, 17, 0, 0, 0, 6, 233, 20, 221, 21, 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