Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 625823a01fd3dcc94b1e57e383d82e9ae6c9788a8410bdfb0e3e5edbd43a0f10

Tx prefix hash: 776d644d501edc73ee2a7398336c8c5e138e5d02fff4c328eb5c3c724a22c4ed
Tx public key: 3f111fb66aab9386c20f71253af3a79e2cc58d5547dec1bedffc136c2aa91e30
Timestamp: 1697986062 Timestamp [UCT]: 2023-10-22 14:47:42 Age [y:d:h:m:s]: 01:093:13:05:49
Block: 875254 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 328060 RingCT/type: yes/0
Extra: 013f111fb66aab9386c20f71253af3a79e2cc58d5547dec1bedffc136c2aa91e3002110000000233af99f4000000000000000000

1 output(s) for total of 0.772538590000 dcy

stealth address amount amount idx
00: 90f9f963f2d6b8ddf4ba9d75a6d990e5ccf9fb4d5efc73d0cc35a9b299868353 0.772538590000 1330504 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": 875264, "vin": [ { "gen": { "height": 875254 } } ], "vout": [ { "amount": 772538590, "target": { "key": "90f9f963f2d6b8ddf4ba9d75a6d990e5ccf9fb4d5efc73d0cc35a9b299868353" } } ], "extra": [ 1, 63, 17, 31, 182, 106, 171, 147, 134, 194, 15, 113, 37, 58, 243, 167, 158, 44, 197, 141, 85, 71, 222, 193, 190, 223, 252, 19, 108, 42, 169, 30, 48, 2, 17, 0, 0, 0, 2, 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