Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5a07d3f0e5b3b256ae7100fbe8f38252b6df57298f7559a2fee73dab41379358

Tx prefix hash: 4fe69ce7de2ecde2259e379a0f716a6510320898fab4e4ce7ff9c052cc14276a
Tx public key: c7899d98f8a55ee276fe012e7ccac548a1175b50306db49a64a4da7c17fe2c29
Timestamp: 1705860750 Timestamp [UCT]: 2024-01-21 18:12:30 Age [y:d:h:m:s]: 01:037:17:37:19
Block: 940305 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 288034 RingCT/type: yes/0
Extra: 01c7899d98f8a55ee276fe012e7ccac548a1175b50306db49a64a4da7c17fe2c2902110000000452d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 769c7ddeec6b9482d0842a4a978987dea7bfa3e40eed3a6c80115970c06fb707 0.600000000000 1398441 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": 940315, "vin": [ { "gen": { "height": 940305 } } ], "vout": [ { "amount": 600000000, "target": { "key": "769c7ddeec6b9482d0842a4a978987dea7bfa3e40eed3a6c80115970c06fb707" } } ], "extra": [ 1, 199, 137, 157, 152, 248, 165, 94, 226, 118, 254, 1, 46, 124, 202, 197, 72, 161, 23, 91, 80, 48, 109, 180, 154, 100, 164, 218, 124, 23, 254, 44, 41, 2, 17, 0, 0, 0, 4, 82, 212, 126, 148, 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