Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9532e00be825d841ab66ce7b5146dc7fc098933dadcb441d6d9cd5ce43053658

Tx prefix hash: 53ac2853f75aa9c4396eb5267c9c7fb526129157016de3768fa8eb67a61eb05f
Tx public key: 0d0af1f79791e920f8349a411c46da4d6eda946650dbc1d2a34129b7d4ff4d63
Timestamp: 1761460802 Timestamp [UCT]: 2025-10-26 06:40:02 Age [y:d:h:m:s]: 00:071:16:06:13
Block: 1398173 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 51334 RingCT/type: yes/0
Extra: 010d0af1f79791e920f8349a411c46da4d6eda946650dbc1d2a34129b7d4ff4d6302110000000125a35a0f000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 31f9102714a9073e5b61f17c32eca4230d1b138b4aa4f57f89a85d9d56be1759 0.600000000000 1886466 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": 1398183, "vin": [ { "gen": { "height": 1398173 } } ], "vout": [ { "amount": 600000000, "target": { "key": "31f9102714a9073e5b61f17c32eca4230d1b138b4aa4f57f89a85d9d56be1759" } } ], "extra": [ 1, 13, 10, 241, 247, 151, 145, 233, 32, 248, 52, 154, 65, 28, 70, 218, 77, 110, 218, 148, 102, 80, 219, 193, 210, 163, 65, 41, 183, 212, 255, 77, 99, 2, 17, 0, 0, 0, 1, 37, 163, 90, 15, 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