← previous blocknext block →recent activity
Analyzing
Block #106,946,835
18 transactions · 17 stateful · 2026-09-22 05:03:28 UTC
Parallelism
78/100
Blocked
35%
Avg conflicts / tx
0.44
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #106,946,835 · 18 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w05w06w18w09w110w111w212w315w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5fad6fee…7714
0x34b655…2a6f
6 touches
3 conflicts
0x70986451…c6bd
0x34b655…2a6f
6 touches
3 conflicts
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0xd192f4ed…d7ec
0x34b655…2a6f
4 touches
1 conflict
0xe720a4c6…8eb0
0x34b655…2a6f
4 touches
1 conflict
0xfa994b26…1ce0
0x34b655…2a6f
4 touches
1 conflict
0x6cad301f…15b7
0x34b655…2a6f
4 touches
1 conflict
0x1f396cee…862f
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
3 conflicts on slot 0x5fad6fee64…277714
Audit this contract →
← previous block·next block →recent activity