Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c2745a268c0c9175b5bf6e9aa1f63a509655e5507c76a8d3bf61b5cc7f86bffd

Tx prefix hash: 7cf425e9b76d03e3880cbed48f4491e58da1190a1e44c0ca5b908603e7f9aa5f
Tx public key: e388af578554bcf5a4d70ebe7c8adb2b510d01511fee57a5719d2272f32c9aba
Timestamp: 1699353347 Timestamp [UCT]: 2023-11-07 10:35:47 Age [y:d:h:m:s]: 01:109:06:12:25
Block: 886387 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0811 kB
Tx version: 2 No of confirmations: 339237 RingCT/type: yes/0
Extra: 01e388af578554bcf5a4d70ebe7c8adb2b510d01511fee57a5719d2272f32c9aba

1 output(s) for total of 0.709629916000 dcy

stealth address amount amount idx
00: bd1c384a79ca696425045abc07d929e969379c71af0ebdb99bd5153dfd8f9cb4 0.709629916000 1342202 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": 886397, "vin": [ { "gen": { "height": 886387 } } ], "vout": [ { "amount": 709629916, "target": { "key": "bd1c384a79ca696425045abc07d929e969379c71af0ebdb99bd5153dfd8f9cb4" } } ], "extra": [ 1, 227, 136, 175, 87, 133, 84, 188, 245, 164, 215, 14, 190, 124, 138, 219, 43, 81, 13, 1, 81, 31, 238, 87, 165, 113, 157, 34, 114, 243, 44, 154, 186 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8