Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f5cf11faf44588a999e63bb5742dc97df7935ce3ec2a3f43dc863be72ec90122

Tx prefix hash: 320d7c2bf967eb6aae2822c30a3dabed99bc4d47fb60649cdc2e0d8efa923ea0
Tx public key: 036cdfedc504a8c3e5e5015c1d627ca95145f511b704ed45a10a51630b57c1cc
Timestamp: 1755936294 Timestamp [UCT]: 2025-08-23 08:04:54 Age [y:d:h:m:s]: 00:038:11:13:35
Block: 1352563 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 27351 RingCT/type: yes/0
Extra: 01036cdfedc504a8c3e5e5015c1d627ca95145f511b704ed45a10a51630b57c1cc021100000001a11dba98000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8619692128dc426c201670f0fee6fbb2281594da2f2d255e073dd2f1a4711577 0.600000000000 1840528 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": 1352573, "vin": [ { "gen": { "height": 1352563 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8619692128dc426c201670f0fee6fbb2281594da2f2d255e073dd2f1a4711577" } } ], "extra": [ 1, 3, 108, 223, 237, 197, 4, 168, 195, 229, 229, 1, 92, 29, 98, 124, 169, 81, 69, 245, 17, 183, 4, 237, 69, 161, 10, 81, 99, 11, 87, 193, 204, 2, 17, 0, 0, 0, 1, 161, 29, 186, 152, 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