Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1145bf8736d8aa4a4d342fa3c85636868e0400937c19c0e94c64a72ef982a8cb

Tx prefix hash: c23bf658a97320e34d8f5fe7b62e8f51dc39419fd771759e91e6c5c444a5bf39
Tx public key: c63f60b290e71a596c0e478c2ca79d53a49011c1ad3f909b10609f6fe85c0d1d
Timestamp: 1701735368 Timestamp [UCT]: 2023-12-05 00:16:08 Age [y:d:h:m:s]: 00:346:03:28:13
Block: 906123 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 247854 RingCT/type: yes/0
Extra: 01c63f60b290e71a596c0e478c2ca79d53a49011c1ad3f909b10609f6fe85c0d1d02110000000be6d27f9c000000000000000000

1 output(s) for total of 0.610433453000 dcy

stealth address amount amount idx
00: a5ea6dd93da6f6d18a04a7ff0a57df63b00494157e053570836d8f7482b5798c 0.610433453000 1363046 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": 906133, "vin": [ { "gen": { "height": 906123 } } ], "vout": [ { "amount": 610433453, "target": { "key": "a5ea6dd93da6f6d18a04a7ff0a57df63b00494157e053570836d8f7482b5798c" } } ], "extra": [ 1, 198, 63, 96, 178, 144, 231, 26, 89, 108, 14, 71, 140, 44, 167, 157, 83, 164, 144, 17, 193, 173, 63, 144, 155, 16, 96, 159, 111, 232, 92, 13, 29, 2, 17, 0, 0, 0, 11, 230, 210, 127, 156, 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