Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a1ff8a158e116925844b0f26096d4a9821a42eb18f951d91dce11539323ab92c

Tx prefix hash: e1c97cbb52d4cb9f16a470d8bfa59fa1339daad6680c2448c7e751608f9339dc
Tx public key: f2c600be2769dcab67f01cc1ec220406b81ab2a0ffa959cdcb320c527dfa4b4e
Timestamp: 1724307591 Timestamp [UCT]: 2024-08-22 06:19:51 Age [y:d:h:m:s]: 00:223:19:24:56
Block: 1093280 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 159798 RingCT/type: yes/0
Extra: 01f2c600be2769dcab67f01cc1ec220406b81ab2a0ffa959cdcb320c527dfa4b4e021100000002e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 64121231f515d704cf2c113dc9a8d16be6c8f23b9ec26cb36e99e6e253905825 0.600000000000 1568193 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": 1093290, "vin": [ { "gen": { "height": 1093280 } } ], "vout": [ { "amount": 600000000, "target": { "key": "64121231f515d704cf2c113dc9a8d16be6c8f23b9ec26cb36e99e6e253905825" } } ], "extra": [ 1, 242, 198, 0, 190, 39, 105, 220, 171, 103, 240, 28, 193, 236, 34, 4, 6, 184, 26, 178, 160, 255, 169, 89, 205, 203, 50, 12, 82, 125, 250, 75, 78, 2, 17, 0, 0, 0, 2, 233, 20, 221, 21, 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