← previous blocknext block →recent activity
Analyzing
Block #106,932,048
19 transactions · 19 stateful · 2026-09-22 03:49:02 UTC
Parallelism
74/100
Blocked
26%
Avg conflicts / tx
0.58
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #106,932,048 · 19 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
1w02w06w09w111w112w216w317w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x2a8ff280…e9ed
0x34b655…2a6f
8 touches
6 conflicts
0xd4230a60…bd13
0x34b655…2a6f
6 touches
3 conflicts
0xd192f4ed…d7ec
0x34b655…2a6f
6 touches
3 conflicts
0xc74116ee…6ec0
0x34b655…2a6f
6 touches
3 conflicts
0x70986451…c6bd
0x34b655…2a6f
6 touches
3 conflicts
0xe4af4c87…9964
0x34b655…2a6f
4 touches
1 conflict
0x49b9fdd5…9c16
0x34b655…2a6f
4 touches
1 conflict
0x4b8ad752…b82a
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
6 conflicts on slot 0x2a8ff2807d…cfe9ed
Audit this contract →
← previous block·next block →recent activity