Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 24c97aa938fe07d3ae1fc68aa1f35b4de4639b072412a8eb550162870c197416

Tx prefix hash: d6758f7fa2b60597004e58843981f72c86fe60168e78ebbef4ace6b0b0be083e
Tx public key: 9e88321df56dfdafdaf68cd45e21ea5a638cdc3a4441d5f07744351f277359f2
Timestamp: 1725398552 Timestamp [UCT]: 2024-09-03 21:22:32 Age [y:d:h:m:s]: 00:081:16:49:39
Block: 1102309 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 58429 RingCT/type: yes/0
Extra: 019e88321df56dfdafdaf68cd45e21ea5a638cdc3a4441d5f07744351f277359f2021100000009e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0c5b3a9b0adad93c695e4b139c4ef827122bbd446ac6e0e66f43fe4651a8ba6f 0.600000000000 1578696 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": 1102319, "vin": [ { "gen": { "height": 1102309 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0c5b3a9b0adad93c695e4b139c4ef827122bbd446ac6e0e66f43fe4651a8ba6f" } } ], "extra": [ 1, 158, 136, 50, 29, 245, 109, 253, 175, 218, 246, 140, 212, 94, 33, 234, 90, 99, 140, 220, 58, 68, 65, 213, 240, 119, 68, 53, 31, 39, 115, 89, 242, 2, 17, 0, 0, 0, 9, 233, 20, 221, 21, 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