Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4fd23b5004fb27059402f5cd1ef6d8fa01593f13f92dcc3e5ce36f73c29c198d

Tx prefix hash: c0fd4b12bdc16a46ac051e34cf1c14b2ec2c9889da1b6187e62e9e347298c319
Tx public key: 51f3e847e7e2aec1e59b4085eba16e864d0f336cd5c62fe622ae10c8f24315c5
Timestamp: 1752788487 Timestamp [UCT]: 2025-07-17 21:41:27 Age [y:d:h:m:s]: 00:030:20:42:33
Block: 1327678 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 20994 RingCT/type: yes/0
Extra: 0151f3e847e7e2aec1e59b4085eba16e864d0f336cd5c62fe622ae10c8f24315c5021100000001dfc3ba49000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4aed1850cece5484ed3758b9c5a52d9ec831c679373a69d51e4a1b5bad30c378 0.600000000000 1815435 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": 1327688, "vin": [ { "gen": { "height": 1327678 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4aed1850cece5484ed3758b9c5a52d9ec831c679373a69d51e4a1b5bad30c378" } } ], "extra": [ 1, 81, 243, 232, 71, 231, 226, 174, 193, 229, 155, 64, 133, 235, 161, 110, 134, 77, 15, 51, 108, 213, 198, 47, 230, 34, 174, 16, 200, 242, 67, 21, 197, 2, 17, 0, 0, 0, 1, 223, 195, 186, 73, 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