Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5a25ccc2735644b6efb77b66ee04fa5e5c0df7f9fd395d490b3debd16f6cd61f

Tx prefix hash: ad6f23a5737b5d5bd634cbe6e9b24ecca73b25a4be1c6b26a47cbc8d785f8141
Tx public key: 9e43ce18779911480aaf4df157773cec9c41434bed66e91a2dc93fcc3f0ce64c
Timestamp: 1723353871 Timestamp [UCT]: 2024-08-11 05:24:31 Age [y:d:h:m:s]: 00:153:00:47:45
Block: 1085359 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 109488 RingCT/type: yes/0
Extra: 019e43ce18779911480aaf4df157773cec9c41434bed66e91a2dc93fcc3f0ce64c021100000001e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 02dab13a76a8e5e8a94017d8a65ed6c3664803ef85fdda3fbf873a3e20a73c71 0.600000000000 1559928 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": 1085369, "vin": [ { "gen": { "height": 1085359 } } ], "vout": [ { "amount": 600000000, "target": { "key": "02dab13a76a8e5e8a94017d8a65ed6c3664803ef85fdda3fbf873a3e20a73c71" } } ], "extra": [ 1, 158, 67, 206, 24, 119, 153, 17, 72, 10, 175, 77, 241, 87, 119, 60, 236, 156, 65, 67, 75, 237, 102, 233, 26, 45, 201, 63, 204, 63, 12, 230, 76, 2, 17, 0, 0, 0, 1, 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