Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8503649e9874be157c4d367fb4c19cda4675627d47428b323db4df8f5d3c2c84

Tx prefix hash: 7efaa8197e77ef0d88ce9bb590fb19078895239a155b87aea6102a009d4144da
Tx public key: c6e6144f2aea257ca7f2a12e23c7835d75c06029562e66de8326673e5aacdf35
Timestamp: 1713696884 Timestamp [UCT]: 2024-04-21 10:54:44 Age [y:d:h:m:s]: 00:153:03:01:49
Block: 1005298 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 109687 RingCT/type: yes/0
Extra: 01c6e6144f2aea257ca7f2a12e23c7835d75c06029562e66de8326673e5aacdf3502110000000c7a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c1559f179c4b919bb56835daf25be5bbc4db78fe3f7e7f0b19133da56152288d 0.600000000000 1465884 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": 1005308, "vin": [ { "gen": { "height": 1005298 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c1559f179c4b919bb56835daf25be5bbc4db78fe3f7e7f0b19133da56152288d" } } ], "extra": [ 1, 198, 230, 20, 79, 42, 234, 37, 124, 167, 242, 161, 46, 35, 199, 131, 93, 117, 192, 96, 41, 86, 46, 102, 222, 131, 38, 103, 62, 90, 172, 223, 53, 2, 17, 0, 0, 0, 12, 122, 156, 244, 199, 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