Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9e69bcb1f9ef680d3e9bbca000e91dacf493fd5e32de8ecd8339cbf719a13d26

Tx prefix hash: b7ba466e0b5f1a8ba3edae839958516b8e83922d23c083864616b21053860da3
Tx public key: a5f909377038ae723fdf6076ebc68b002189a5f4e839b34719714f7c4da5e6ee
Timestamp: 1746402022 Timestamp [UCT]: 2025-05-04 23:40:22 Age [y:d:h:m:s]: 00:198:20:12:26
Block: 1275919 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 139822 RingCT/type: yes/0
Extra: 01a5f909377038ae723fdf6076ebc68b002189a5f4e839b34719714f7c4da5e6ee0211000000021f90517a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 08acfc2bb08002a3137be7a98a006c5bebbd05f90244d8f935a2c912e330d90e 0.600000000000 1763234 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": 1275929, "vin": [ { "gen": { "height": 1275919 } } ], "vout": [ { "amount": 600000000, "target": { "key": "08acfc2bb08002a3137be7a98a006c5bebbd05f90244d8f935a2c912e330d90e" } } ], "extra": [ 1, 165, 249, 9, 55, 112, 56, 174, 114, 63, 223, 96, 118, 235, 198, 139, 0, 33, 137, 165, 244, 232, 57, 179, 71, 25, 113, 79, 124, 77, 165, 230, 238, 2, 17, 0, 0, 0, 2, 31, 144, 81, 122, 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