Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 394b37ecaf1e129b961f71fbee2f50b0ae956bc7c7369b6a019db56123cdadd0

Tx prefix hash: 5440e7fecbe22e8b5fbd8d1c9323b3688335a4ad577ca5d7c2b03b4da1f76df3
Tx public key: 71a067082cb09d51f6e91455664ab9463f963a4b783edbc634413048827f0455
Timestamp: 1752499636 Timestamp [UCT]: 2025-07-14 13:27:16 Age [y:d:h:m:s]: 00:200:14:39:03
Block: 1325341 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 142018 RingCT/type: yes/0
Extra: 0171a067082cb09d51f6e91455664ab9463f963a4b783edbc634413048827f045502110000000843846d66000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e41ae77ae82607070b7c6fce7d894b54747e8ca28e5b37d7f6b93c35b7f8f3a3 0.600000000000 1813086 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": 1325351, "vin": [ { "gen": { "height": 1325341 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e41ae77ae82607070b7c6fce7d894b54747e8ca28e5b37d7f6b93c35b7f8f3a3" } } ], "extra": [ 1, 113, 160, 103, 8, 44, 176, 157, 81, 246, 233, 20, 85, 102, 74, 185, 70, 63, 150, 58, 75, 120, 62, 219, 198, 52, 65, 48, 72, 130, 127, 4, 85, 2, 17, 0, 0, 0, 8, 67, 132, 109, 102, 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