Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: efd1f153e28745c0b90f3bb0e65abb69390a4dae855081a7ebaf4d9abb29fc4f

Tx prefix hash: 682ed5f35af5995e4fb19e85b9d6c6cec0949329c0254631c07cc9bb562b88c4
Tx public key: d23ebec42b4a4b29dcad490a076db31240425ea529d19af3d795b4a92e894f87
Timestamp: 1710643156 Timestamp [UCT]: 2024-03-17 02:39:16 Age [y:d:h:m:s]: 01:234:05:59:02
Block: 980002 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 426079 RingCT/type: yes/0
Extra: 01d23ebec42b4a4b29dcad490a076db31240425ea529d19af3d795b4a92e894f870211000000057a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 07fe7eeb401888bbe2e3b88db7e7edaecadfc2125750fd348a5908ace75a74c5 0.600000000000 1440059 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": 980012, "vin": [ { "gen": { "height": 980002 } } ], "vout": [ { "amount": 600000000, "target": { "key": "07fe7eeb401888bbe2e3b88db7e7edaecadfc2125750fd348a5908ace75a74c5" } } ], "extra": [ 1, 210, 62, 190, 196, 43, 74, 75, 41, 220, 173, 73, 10, 7, 109, 179, 18, 64, 66, 94, 165, 41, 209, 154, 243, 215, 149, 180, 169, 46, 137, 79, 135, 2, 17, 0, 0, 0, 5, 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