← previous blocknext block →recent activity
Analyzing
Block #94,319,097
20 transactions · 19 stateful · 2026-08-08 22:04:42 UTC
Parallelism
70/100
Blocked
58%
Avg conflicts / tx
1.15
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #94,319,097 · 20 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w14w05w16w27w18w29w310w413w514w315w519w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa86351b8…2c5a
0x34b655…2a6f
10 touches
10 conflicts
0xca841faa…486a
0x34b655…2a6f
8 touches
6 conflicts
0xe5bb3628…e5f1
0x34b655…2a6f
8 touches
6 conflicts
0xdd190722…ecae
0x34b655…2a6f
6 touches
3 conflicts
0x5d5a6305…73e9
0x34b655…2a6f
6 touches
3 conflicts
0x1bee5aea…5f61
0x34b655…2a6f
6 touches
3 conflicts
0x3ba5c1dd…c62b
0x34b655…2a6f
4 touches
1 conflict
0x3fff7ccd…5a48
0x34b655…2a6f
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: Perpl
10 conflicts on slot 0xa86351b861…d52c5a
Audit this contract →
← previous block·next block →recent activity