Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b89711119a74a5dadbab479a1d4f54f5760aaf392444976d427a08ff6034253e

Tx prefix hash: ccebfaaadb060d38f1c6bcb3e1b86763a7dfdc368d9c58a37fb61fe343988a50
Tx public key: f165811d0d64799ef0b4e9af5360598e68d1a3dc9b6729c41337df0e645d1f7f
Timestamp: 1760833493 Timestamp [UCT]: 2025-10-19 00:24:53 Age [y:d:h:m:s]: 00:026:05:45:19
Block: 1392982 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 18774 RingCT/type: yes/0
Extra: 01f165811d0d64799ef0b4e9af5360598e68d1a3dc9b6729c41337df0e645d1f7f02110000000101491f88000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6ce99cf8d5a14be70ef9b98149683124d950bb8f77f25b724fd730c8cd27cab3 0.600000000000 1881239 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": 1392992, "vin": [ { "gen": { "height": 1392982 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6ce99cf8d5a14be70ef9b98149683124d950bb8f77f25b724fd730c8cd27cab3" } } ], "extra": [ 1, 241, 101, 129, 29, 13, 100, 121, 158, 240, 180, 233, 175, 83, 96, 89, 142, 104, 209, 163, 220, 155, 103, 41, 196, 19, 55, 223, 14, 100, 93, 31, 127, 2, 17, 0, 0, 0, 1, 1, 73, 31, 136, 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