Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 765caadb4b99ce91e956937a6ca26416791aea91baaf9c7c601b37be44115224

Tx prefix hash: c4a16941e1eb999688025bf0d52107816dfe38cef29a25a69fab4b3c036bd830
Tx public key: 176dff3e603e208716ce02ac88d4969d2ce9fd3831b41673f9d3c3d9484328e2
Timestamp: 1699457385 Timestamp [UCT]: 2023-11-08 15:29:45 Age [y:d:h:m:s]: 02:001:14:20:07
Block: 887255 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 520907 RingCT/type: yes/0
Extra: 01176dff3e603e208716ce02ac88d4969d2ce9fd3831b41673f9d3c3d9484328e202110000000133af99f4000000000000000000

1 output(s) for total of 0.704946031000 dcy

stealth address amount amount idx
00: 61ceb1a8506ab47bf03505b6ca953b485c29e5f3444357262ac049619dc3e767 0.704946031000 1343124 of 0

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": 887265, "vin": [ { "gen": { "height": 887255 } } ], "vout": [ { "amount": 704946031, "target": { "key": "61ceb1a8506ab47bf03505b6ca953b485c29e5f3444357262ac049619dc3e767" } } ], "extra": [ 1, 23, 109, 255, 62, 96, 62, 32, 135, 22, 206, 2, 172, 136, 212, 150, 157, 44, 233, 253, 56, 49, 180, 22, 115, 249, 211, 195, 217, 72, 67, 40, 226, 2, 17, 0, 0, 0, 1, 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