Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 35832ea34b19dd682ce86250ceaf24c9f0842b76b328d9f103b38058e53de52e

Tx prefix hash: 92d607aaf3d2122b0a12f5468ea704eaacd2f55211b61253907ab752a1915e2e
Tx public key: 513c90af255c6d30c99ca6a5b67d6af74f38205c8ac264986a5185aa15ff5c4e
Timestamp: 1762897585 Timestamp [UCT]: 2025-11-11 21:46:25 Age [y:d:h:m:s]: 00:016:08:10:48
Block: 1410070 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 11705 RingCT/type: yes/0
Extra: 01513c90af255c6d30c99ca6a5b67d6af74f38205c8ac264986a5185aa15ff5c4e021100000001dfc3ba49000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8395a2f0a2017569db4cbeb5a3a13fda37a114266f254e2d6cc8f67c9e0da157 0.600000000000 1898519 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": 1410080, "vin": [ { "gen": { "height": 1410070 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8395a2f0a2017569db4cbeb5a3a13fda37a114266f254e2d6cc8f67c9e0da157" } } ], "extra": [ 1, 81, 60, 144, 175, 37, 92, 109, 48, 201, 156, 166, 165, 182, 125, 106, 247, 79, 56, 32, 92, 138, 194, 100, 152, 106, 81, 133, 170, 21, 255, 92, 78, 2, 17, 0, 0, 0, 1, 223, 195, 186, 73, 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