Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 320be0c8c6fbf133f026675c7f4522baf75f0c4c554ff4a54dbe383a5154e7ca

Tx prefix hash: e7f9ea9933e196da92ae4e724b74da24963af79885e524d1bacc163a89ba5b06
Tx public key: 76a2d1a57c3cc970aee3c6193905e9ebb1d27b1bae0fd0e54604e2ef7bcfb7ff
Timestamp: 1728937646 Timestamp [UCT]: 2024-10-14 20:27:26 Age [y:d:h:m:s]: 00:358:23:54:34
Block: 1131651 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 254025 RingCT/type: yes/0
Extra: 0176a2d1a57c3cc970aee3c6193905e9ebb1d27b1bae0fd0e54604e2ef7bcfb7ff021100000001e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0a7c19997e6c633e60e8402f4e96e017caf0230159562505efdc1bdea1c3810e 0.600000000000 1614554 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": 1131661, "vin": [ { "gen": { "height": 1131651 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0a7c19997e6c633e60e8402f4e96e017caf0230159562505efdc1bdea1c3810e" } } ], "extra": [ 1, 118, 162, 209, 165, 124, 60, 201, 112, 174, 227, 198, 25, 57, 5, 233, 235, 177, 210, 123, 27, 174, 15, 208, 229, 70, 4, 226, 239, 123, 207, 183, 255, 2, 17, 0, 0, 0, 1, 233, 20, 221, 21, 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