Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 56f2bbfe5d1d3d1f1d9b535424f49e0d2579ea67e780aa67daf79d09cbe0cec7

Tx prefix hash: d521ea4db4219b7948d500a00fa46cbc354c91c77fe7a4579a6c02de93f313ea
Tx public key: 4a26d86fd17c8b5717825589bdc1d0b7e7fbcb9b05c003dc83175eb6e5776286
Timestamp: 1765061649 Timestamp [UCT]: 2025-12-06 22:54:09 Age [y:d:h:m:s]: 00:034:00:06:50
Block: 1428007 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 24364 RingCT/type: yes/0
Extra: 014a26d86fd17c8b5717825589bdc1d0b7e7fbcb9b05c003dc83175eb6e5776286021100000011d6e19d7c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f75d7be193f08212251f51a3fa64c397f4b03d0a293d87acca3f8193e587994c 0.600000000000 1916716 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": 1428017, "vin": [ { "gen": { "height": 1428007 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f75d7be193f08212251f51a3fa64c397f4b03d0a293d87acca3f8193e587994c" } } ], "extra": [ 1, 74, 38, 216, 111, 209, 124, 139, 87, 23, 130, 85, 137, 189, 193, 208, 183, 231, 251, 203, 155, 5, 192, 3, 220, 131, 23, 94, 182, 229, 119, 98, 134, 2, 17, 0, 0, 0, 17, 214, 225, 157, 124, 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