← previous blocknext block →recent activity
Analyzing
Block #94,760,217
29 transactions · 27 stateful · 2026-08-10 11:12:53 UTC
Parallelism
83/100
Blocked
30%
Avg conflicts / tx
0.59
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #94,760,217 · 29 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w15w06w27w18w09w110w211w312w413w023w026w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0002
0xeae24c…0be0
10 touches
10 conflicts
0x90c91fbc…40d4
0xd32edf…ff58
5 touches
3 conflicts
0x52e69143…95ad
0x065c9d…c394
4 touches
1 conflict
0x00000000…002a
0x1b6862…e19c
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x00000000…001a
0x1b6862…e19c
4 touches
1 conflict
0xc2aacf41…54ff
0x1b6862…e19c
4 touches
1 conflict
0xd9f18d9a…141d
0x1b6862…e19c
4 touches
1 conflict
What's blocking what?
Click any transaction in the timeline or graph to see which storage slots forced it to wait, and which later transactions it blocked.
The bottleneck
Throughput-killer: 0xeae24c72…e30be0
10 conflicts on slot 0x0000000000…000002
Audit this contract →
← previous block·next block →recent activity