Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c4ab260dfc01d8e686ab0b451031bbff3d426128463d697e44feba5070359fed

Tx prefix hash: 8987fc783c218c74c34431f81faed33ce57f2b61550227a646aa6d3a1cb3e84d
Tx public key: 89b6b4fb7d7f3e7fe523fcc425876d1c051009a9b7d236ca7b6df2d1bf88d047
Timestamp: 1761254794 Timestamp [UCT]: 2025-10-23 21:26:34 Age [y:d:h:m:s]: 00:060:12:43:23
Block: 1396473 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 43314 RingCT/type: yes/0
Extra: 0189b6b4fb7d7f3e7fe523fcc425876d1c051009a9b7d236ca7b6df2d1bf88d047021100000001e4dc9009000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0a5107e4e1f12901c2b918048c10e8d0cab05fb4d2a46fdd288b9848c028933c 0.600000000000 1884760 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": 1396483, "vin": [ { "gen": { "height": 1396473 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0a5107e4e1f12901c2b918048c10e8d0cab05fb4d2a46fdd288b9848c028933c" } } ], "extra": [ 1, 137, 182, 180, 251, 125, 127, 62, 127, 229, 35, 252, 196, 37, 135, 109, 28, 5, 16, 9, 169, 183, 210, 54, 202, 123, 109, 242, 209, 191, 136, 208, 71, 2, 17, 0, 0, 0, 1, 228, 220, 144, 9, 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