Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4a5f72159f6f4832c36c2647234da47fac1a243db9a0f61ae2bd2701931767fb

Tx prefix hash: 65cb871c9ab902b181a49d3ff65b28d4da5127619fae494427d9a58018ef2ca3
Tx public key: a320285c6cc537b416156224f3a1eacbe53f73ba4d3cde65bef2d9698d0d2349
Timestamp: 1744444816 Timestamp [UCT]: 2025-04-12 08:00:16 Age [y:d:h:m:s]: 00:296:05:10:44
Block: 1259715 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 209349 RingCT/type: yes/0
Extra: 01a320285c6cc537b416156224f3a1eacbe53f73ba4d3cde65bef2d9698d0d234902110000000c6c98aa3d000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1080a9eb7e124ab8ace6d9acf98a2a3b428c7ffe2a624548bd30cf24d97ee25f 0.600000000000 1746864 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": 1259725, "vin": [ { "gen": { "height": 1259715 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1080a9eb7e124ab8ace6d9acf98a2a3b428c7ffe2a624548bd30cf24d97ee25f" } } ], "extra": [ 1, 163, 32, 40, 92, 108, 197, 55, 180, 22, 21, 98, 36, 243, 161, 234, 203, 229, 63, 115, 186, 77, 60, 222, 101, 190, 242, 217, 105, 141, 13, 35, 73, 2, 17, 0, 0, 0, 12, 108, 152, 170, 61, 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