Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 66113a1e01ac2780e78eb7cd7c37e7f4f06fb84a4a63263c0a0f35ae32b24712

Tx prefix hash: 8a3703dc7b2682b1eb2ac04be3173af584df0988d66ad870462365873a829255
Tx public key: 78b155db577013cb0e5d293e17c5ec1ec978c289d42091fca667e848a305c49e
Timestamp: 1756841596 Timestamp [UCT]: 2025-09-02 19:33:16 Age [y:d:h:m:s]: 00:116:22:58:52
Block: 1359953 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 83678 RingCT/type: yes/0
Extra: 0178b155db577013cb0e5d293e17c5ec1ec978c289d42091fca667e848a305c49e021100000002b2f784c4000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e3e15aeee4d98f04d11c1d0af8d257b9bfc7447de8dff1fc00c74bc6020375b0 0.600000000000 1847966 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": 1359963, "vin": [ { "gen": { "height": 1359953 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e3e15aeee4d98f04d11c1d0af8d257b9bfc7447de8dff1fc00c74bc6020375b0" } } ], "extra": [ 1, 120, 177, 85, 219, 87, 112, 19, 203, 14, 93, 41, 62, 23, 197, 236, 30, 201, 120, 194, 137, 212, 32, 145, 252, 166, 103, 232, 72, 163, 5, 196, 158, 2, 17, 0, 0, 0, 2, 178, 247, 132, 196, 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