Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8dc66d501b5fb136a3b6f89aa317fff80d169db879f81bd278c06c2e67af1cf6

Tx prefix hash: 01f61fad23b67e2203568e98a7db5396871e582ce041dad86cf723c1e30af1be
Tx public key: 5199d7dc4fdf1f1cdff3f1a94413477227c25187bb7be37ee53e154c9b21cc06
Timestamp: 1759396760 Timestamp [UCT]: 2025-10-02 09:19:20 Age [y:d:h:m:s]: 00:007:03:29:43
Block: 1381056 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 5114 RingCT/type: yes/0
Extra: 015199d7dc4fdf1f1cdff3f1a94413477227c25187bb7be37ee53e154c9b21cc0602110000000497baf922000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: cc42ad507e2f5a0f5d8a9aac922807c1e816bfb1ced8c6ba9e2e4852dea7915c 0.600000000000 1869169 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": 1381066, "vin": [ { "gen": { "height": 1381056 } } ], "vout": [ { "amount": 600000000, "target": { "key": "cc42ad507e2f5a0f5d8a9aac922807c1e816bfb1ced8c6ba9e2e4852dea7915c" } } ], "extra": [ 1, 81, 153, 215, 220, 79, 223, 31, 28, 223, 243, 241, 169, 68, 19, 71, 114, 39, 194, 81, 135, 187, 123, 227, 126, 229, 62, 21, 76, 155, 33, 204, 6, 2, 17, 0, 0, 0, 4, 151, 186, 249, 34, 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