Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6668c24a6c6b5fd3474ca4b1a3d1513a12619897cc95268cb646fab46abc5d74

Tx prefix hash: bd579685020b0be55b6df1b1d5c04a67d39cb32458b0789811df88d46f3f91ba
Tx public key: 390a1b2523aad24f714846cb525ac6565d6693870b2fe9b38588f5b404915435
Timestamp: 1658240013 Timestamp [UCT]: 2022-07-19 14:13:33 Age [y:d:h:m:s]: 02:245:07:34:05
Block: 547173 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 696516 RingCT/type: yes/0
Extra: 01390a1b2523aad24f714846cb525ac6565d6693870b2fe9b38588f5b4049154350211000000012e6b1fd5000000000000000000

1 output(s) for total of 9.440366283000 dcy

stealth address amount amount idx
00: e3079b4244cdbf8fa31b8c261cc6d83fdd1ef22ef8db79c1f260142a9782a1f7 9.440366283000 978282 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": 547183, "vin": [ { "gen": { "height": 547173 } } ], "vout": [ { "amount": 9440366283, "target": { "key": "e3079b4244cdbf8fa31b8c261cc6d83fdd1ef22ef8db79c1f260142a9782a1f7" } } ], "extra": [ 1, 57, 10, 27, 37, 35, 170, 210, 79, 113, 72, 70, 203, 82, 90, 198, 86, 93, 102, 147, 135, 11, 47, 233, 179, 133, 136, 245, 180, 4, 145, 84, 53, 2, 17, 0, 0, 0, 1, 46, 107, 31, 213, 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