Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 16bbef02399e3f1e31953f9e60bb1398e148940b2c6f274bd84712d2f9ae98c4

Tx prefix hash: 2fe21815c6f30ec96afae291d2b4c0aa740048fdcbf98540d55e6dfe8f03014f
Tx public key: 8195419acfe0895397161e83993c2f92d0a58552cc1d6d725f7ef314a1976bc4
Timestamp: 1708830589 Timestamp [UCT]: 2024-02-25 03:09:49 Age [y:d:h:m:s]: 01:037:13:56:05
Block: 964956 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 287873 RingCT/type: yes/0
Extra: 018195419acfe0895397161e83993c2f92d0a58552cc1d6d725f7ef314a1976bc40211000000020546d7d0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1ec4fce218b7ba921dc5271813580cc1020f4e3e9133c5f50e7c87dd87a700db 0.600000000000 1424699 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": 964966, "vin": [ { "gen": { "height": 964956 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1ec4fce218b7ba921dc5271813580cc1020f4e3e9133c5f50e7c87dd87a700db" } } ], "extra": [ 1, 129, 149, 65, 154, 207, 224, 137, 83, 151, 22, 30, 131, 153, 60, 47, 146, 208, 165, 133, 82, 204, 29, 109, 114, 95, 126, 243, 20, 161, 151, 107, 196, 2, 17, 0, 0, 0, 2, 5, 70, 215, 208, 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