Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f5e0f7ddc89ad5c204a021d364862c15e081f689b89f7705c721e7dc7684742b

Tx prefix hash: 0853fc0aca3fa8b8039c24f1e459c299b0e180333e9183097c34eaf08d3a79ac
Tx public key: 0f4a7a7d9109703f528ed54183d008dff5507440da9f488e607757d189f08699
Timestamp: 1725759159 Timestamp [UCT]: 2024-09-08 01:32:39 Age [y:d:h:m:s]: 00:203:09:12:28
Block: 1105300 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 145189 RingCT/type: yes/0
Extra: 010f4a7a7d9109703f528ed54183d008dff5507440da9f488e607757d189f0869902110000000a91e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 508928c93c86b3d9e71f790c345692f3c2aac84d9482a66bd7d0c10cf8deaeff 0.600000000000 1582641 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": 1105310, "vin": [ { "gen": { "height": 1105300 } } ], "vout": [ { "amount": 600000000, "target": { "key": "508928c93c86b3d9e71f790c345692f3c2aac84d9482a66bd7d0c10cf8deaeff" } } ], "extra": [ 1, 15, 74, 122, 125, 145, 9, 112, 63, 82, 142, 213, 65, 131, 208, 8, 223, 245, 80, 116, 64, 218, 159, 72, 142, 96, 119, 87, 209, 137, 240, 134, 153, 2, 17, 0, 0, 0, 10, 145, 225, 60, 4, 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