Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a2f8e9654ca72acfb317c04cdfca4a812027117c1d41d2e90c0404905931755e

Tx prefix hash: bde7dd56b5f55d757429bc3ae37a177227d642307181dd3ebb0399c86f70930c
Tx public key: c687b39c67c2409b8a55d8611db9cf444d077fe28cb4bd16d3da1389ed083e1e
Timestamp: 1702746965 Timestamp [UCT]: 2023-12-16 17:16:05 Age [y:d:h:m:s]: 01:074:01:37:28
Block: 914519 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 314033 RingCT/type: yes/0
Extra: 01c687b39c67c2409b8a55d8611db9cf444d077fe28cb4bd16d3da1389ed083e1e02110000000933af99f4000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bf9ad38781fc68e1bf8d8e802bf6a5bbe616e79ae9c46026e5a281b08155a8b6 0.600000000000 1371835 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": 914529, "vin": [ { "gen": { "height": 914519 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bf9ad38781fc68e1bf8d8e802bf6a5bbe616e79ae9c46026e5a281b08155a8b6" } } ], "extra": [ 1, 198, 135, 179, 156, 103, 194, 64, 155, 138, 85, 216, 97, 29, 185, 207, 68, 77, 7, 127, 226, 140, 180, 189, 22, 211, 218, 19, 137, 237, 8, 62, 30, 2, 17, 0, 0, 0, 9, 51, 175, 153, 244, 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