← previous blocknext block →recent activity
Analyzing
Block #93,933,118
17 transactions · 15 stateful · 2026-08-07 13:35:25 UTC
Parallelism
65/100
Blocked
53%
Avg conflicts / tx
1.29
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #93,933,118 · 17 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
1w02w14w05w06w17w29w310w411w514w216w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xca841faa…486a
0x34b655…2a6f
12 touches
15 conflicts
0x2bcdd4a1…3d3a
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…003d
0xa6afd3…d132
6 touches
3 conflicts
0x45ef9175…5ab2
0x34b655…2a6f
6 touches
3 conflicts
0xf1a14809…56fd
0x2b46c0…1669
4 touches
1 conflict
0x00e21a9f…3583
0x34b655…2a6f
4 touches
1 conflict
0x3c78ca04…432c
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
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
15 conflicts on slot 0xca841faae5…71486a
Audit this contract →
← previous block·next block →recent activity