Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 53c52f2794c1f1d00422da544dff2240dfe2022bf7bacd07d608a734eb616202

Tx prefix hash: 0a18807a76aac73b4c7c5e2c4f6ee7412a6375bbd14281bb52590b6a9ec1b02e
Tx public key: 2afd6b98a9b4d3df9840f2f7d155ad47b22c64036c368831cf3437e46edaf8fd
Timestamp: 1759965953 Timestamp [UCT]: 2025-10-08 23:25:53 Age [y:d:h:m:s]: 00:115:10:39:58
Block: 1385770 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 82485 RingCT/type: yes/0
Extra: 012afd6b98a9b4d3df9840f2f7d155ad47b22c64036c368831cf3437e46edaf8fd021100000014a5dccd79000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ff4f5eccaa441fd523de1e8f4e13c478bcfa95f3050db499be7afdb127ff923b 0.600000000000 1873933 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": 1385780, "vin": [ { "gen": { "height": 1385770 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ff4f5eccaa441fd523de1e8f4e13c478bcfa95f3050db499be7afdb127ff923b" } } ], "extra": [ 1, 42, 253, 107, 152, 169, 180, 211, 223, 152, 64, 242, 247, 209, 85, 173, 71, 178, 44, 100, 3, 108, 54, 136, 49, 207, 52, 55, 228, 110, 218, 248, 253, 2, 17, 0, 0, 0, 20, 165, 220, 205, 121, 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