Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d68715e26cdc630fb5ae43af714271ca49ac1f260e0142f274ef98fa979e5fd4

Tx prefix hash: cc8c3da3a8731cf31afe1335d99b9866bc82ef524ae0bc2e04a4ae897b97860d
Tx public key: 66094ab935c6cf5b58bb8b25db0ee144a753d2680158d07334de7ac9ee224b5b
Timestamp: 1754633494 Timestamp [UCT]: 2025-08-08 06:11:34 Age [y:d:h:m:s]: 00:105:06:17:03
Block: 1342636 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 74307 RingCT/type: yes/0
Extra: 0166094ab935c6cf5b58bb8b25db0ee144a753d2680158d07334de7ac9ee224b5b021100000004ad7948d0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2fd5327a577e53a87fc83944fee2a7c664b65e966dea0f8069c9bd75b90437e7 0.600000000000 1830469 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": 1342646, "vin": [ { "gen": { "height": 1342636 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2fd5327a577e53a87fc83944fee2a7c664b65e966dea0f8069c9bd75b90437e7" } } ], "extra": [ 1, 102, 9, 74, 185, 53, 198, 207, 91, 88, 187, 139, 37, 219, 14, 225, 68, 167, 83, 210, 104, 1, 88, 208, 115, 52, 222, 122, 201, 238, 34, 75, 91, 2, 17, 0, 0, 0, 4, 173, 121, 72, 208, 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