Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 62bc5e4d6f8cf502d58f8d63707a0914d4fea4dd3e99476ddca6c58600b842b6

Tx prefix hash: 7d3a628283d2273252110ba0825adc6811bd0a712a5519ba8e2e64e4629a236e
Tx public key: b3e823e74310424c84847d624f9948fc0815e0c1980af5bee8e5bbf2d82c3ce2
Timestamp: 1710168923 Timestamp [UCT]: 2024-03-11 14:55:23 Age [y:d:h:m:s]: 01:031:17:03:15
Block: 976066 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 283649 RingCT/type: yes/0
Extra: 01b3e823e74310424c84847d624f9948fc0815e0c1980af5bee8e5bbf2d82c3ce20211000000050011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 51137e40bff5e036ed25c4d5907cd03167ae6a518feeec5cc76586a5337fc8dc 0.600000000000 1436053 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": 976076, "vin": [ { "gen": { "height": 976066 } } ], "vout": [ { "amount": 600000000, "target": { "key": "51137e40bff5e036ed25c4d5907cd03167ae6a518feeec5cc76586a5337fc8dc" } } ], "extra": [ 1, 179, 232, 35, 231, 67, 16, 66, 76, 132, 132, 125, 98, 79, 153, 72, 252, 8, 21, 224, 193, 152, 10, 245, 190, 232, 229, 187, 242, 216, 44, 60, 226, 2, 17, 0, 0, 0, 5, 0, 17, 5, 91, 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