← previous blocknext block →recent activity
Analyzing
Block #106,935,587
25 transactions · 24 stateful · 2026-09-22 04:06:51 UTC
Parallelism
80/100
Blocked
33%
Avg conflicts / tx
0.68
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #106,935,587 · 25 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
2w04w19w011w112w213w320w221w322w223w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfcd5e68f…2a12
0x34b655…2a6f
8 touches
6 conflicts
0x469dac8d…3411
0x34b655…2a6f
8 touches
6 conflicts
0x087bd8a7…5a10
0x34b655…2a6f
6 touches
3 conflicts
0x229d2b7e…abdf
0x34b655…2a6f
6 touches
3 conflicts
0x9d6a99f9…da64
0x34b655…2a6f
6 touches
3 conflicts
0xccebf5c5…8758
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0xe1c4e5ce…0dec
0x34b655…2a6f
6 touches
3 conflicts
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
6 conflicts on slot 0xfcd5e68f28…382a12
Audit this contract →
← previous block·next block →recent activity