Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: abf6a4b6fe5616a3a6a89b5e7a6b8541eeb2314029a2727af4da52f3d382bca6

Tx prefix hash: ea324a6b16ed3eb0b835ddab047528d53b2199f0a5c17561b05c4a5871def8d6
Tx public key: 5798b1ab0201d5efc77aed3bbd139b360a2b3fe66fb44ac253e850dae33412ab
Timestamp: 1700325400 Timestamp [UCT]: 2023-11-18 16:36:40 Age [y:d:h:m:s]: 01:139:07:51:26
Block: 894444 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 360749 RingCT/type: yes/0
Extra: 015798b1ab0201d5efc77aed3bbd139b360a2b3fe66fb44ac253e850dae33412ab02110000000575e3f0e9000000000000000000

1 output(s) for total of 0.667322423000 dcy

stealth address amount amount idx
00: d3bbbd230ffd4a386bcc6839c45ec6df9f19e7a6e69aa8ee10bfcf73a9f3c2c4 0.667322423000 1350643 of 0

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": 894454, "vin": [ { "gen": { "height": 894444 } } ], "vout": [ { "amount": 667322423, "target": { "key": "d3bbbd230ffd4a386bcc6839c45ec6df9f19e7a6e69aa8ee10bfcf73a9f3c2c4" } } ], "extra": [ 1, 87, 152, 177, 171, 2, 1, 213, 239, 199, 122, 237, 59, 189, 19, 155, 54, 10, 43, 63, 230, 111, 180, 74, 194, 83, 232, 80, 218, 227, 52, 18, 171, 2, 17, 0, 0, 0, 5, 117, 227, 240, 233, 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