Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0069afbb8416c1af0d0d03a0a0339a15f35db81ab8cd3ecd0bac17bd29374c12

Tx prefix hash: eea6c03a298a385694291d5658aad384ef76927fd841bb523ed5e3bfd2905054
Tx public key: a0995d6511a61bc77e9f6a097d28ae00d2310f2e441ee2bae40a48c0b206c0e6
Timestamp: 1762060831 Timestamp [UCT]: 2025-11-02 05:20:31 Age [y:d:h:m:s]: 00:004:16:56:08
Block: 1403143 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 3362 RingCT/type: yes/0
Extra: 01a0995d6511a61bc77e9f6a097d28ae00d2310f2e441ee2bae40a48c0b206c0e6021100000002e4dc9009000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8c6da07040fa58a855801f48142dea6890d1a0b75cf93b1f9d629b1c4d79420d 0.600000000000 1891470 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": 1403153, "vin": [ { "gen": { "height": 1403143 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8c6da07040fa58a855801f48142dea6890d1a0b75cf93b1f9d629b1c4d79420d" } } ], "extra": [ 1, 160, 153, 93, 101, 17, 166, 27, 199, 126, 159, 106, 9, 125, 40, 174, 0, 210, 49, 15, 46, 68, 30, 226, 186, 228, 10, 72, 192, 178, 6, 192, 230, 2, 17, 0, 0, 0, 2, 228, 220, 144, 9, 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