Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8f4614d2628abcb6cd00c21cf998b62cbcc21df7fbcd82c94235cecf23bbf0bf

Tx prefix hash: 2e4d3f90d7bda7e60add471a9bfc01969173169cb4f54e541a9d64627261e80d
Tx public key: ed8909d28e07a2970bdbce2ea1d9cfa26471f63c99e9232ef48782a4528c75c4
Timestamp: 1752672951 Timestamp [UCT]: 2025-07-16 13:35:51 Age [y:d:h:m:s]: 00:074:05:23:57
Block: 1326743 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 51729 RingCT/type: yes/0
Extra: 01ed8909d28e07a2970bdbce2ea1d9cfa26471f63c99e9232ef48782a4528c75c4021100000002e4dc9009000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1ab25221955f8e09d0db7f05c5246b2476dc9d87f73dbedbfcb45831289cad4c 0.600000000000 1814496 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": 1326753, "vin": [ { "gen": { "height": 1326743 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1ab25221955f8e09d0db7f05c5246b2476dc9d87f73dbedbfcb45831289cad4c" } } ], "extra": [ 1, 237, 137, 9, 210, 142, 7, 162, 151, 11, 219, 206, 46, 161, 217, 207, 162, 100, 113, 246, 60, 153, 233, 35, 46, 244, 135, 130, 164, 82, 140, 117, 196, 2, 17, 0, 0, 0, 2, 228, 220, 144, 9, 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