Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: befa1f963e943db2ce92ce3b09a6538dd78a2fbdd7def75ba647fef3e6bdfcbe

Tx prefix hash: 65af40a813e61579d066904fc6a882e6df542e8b250df9ceaf906ae56c5a20dd
Tx public key: f323311c4e08703174ee681261e5b2a3300ca587a7d31c3d92b99631eb0bd43c
Timestamp: 1752426786 Timestamp [UCT]: 2025-07-13 17:13:06 Age [y:d:h:m:s]: 00:166:13:24:26
Block: 1324737 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 117817 RingCT/type: yes/0
Extra: 01f323311c4e08703174ee681261e5b2a3300ca587a7d31c3d92b99631eb0bd43c0211000000022609b3a0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2edb77f9406149c1764cab6dd83c0b951b123b4edd059b46da3eec81f9229501 0.600000000000 1812480 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": 1324747, "vin": [ { "gen": { "height": 1324737 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2edb77f9406149c1764cab6dd83c0b951b123b4edd059b46da3eec81f9229501" } } ], "extra": [ 1, 243, 35, 49, 28, 78, 8, 112, 49, 116, 238, 104, 18, 97, 229, 178, 163, 48, 12, 165, 135, 167, 211, 28, 61, 146, 185, 150, 49, 235, 11, 212, 60, 2, 17, 0, 0, 0, 2, 38, 9, 179, 160, 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