← previous blocknext block →recent activity
Analyzing
Block #106,924,142
33 transactions · 30 stateful · 2026-09-22 03:09:15 UTC
Parallelism
82/100
Blocked
53%
Avg conflicts / tx
1.09
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #106,924,142 · 33 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
2w04w05w16w07w18w19w210w311w012w213w314w415w520w422w125w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xba1edffb…323e
0x34b655…2a6f
10 touches
10 conflicts
0x75ec3324…5525
0x34b655…2a6f
10 touches
10 conflicts
0xccebf5c5…8758
0x34b655…2a6f
10 touches
10 conflicts
0xe720a4c6…8eb0
0x34b655…2a6f
10 touches
10 conflicts
0xdf64e5e6…75e8
0x34b655…2a6f
10 touches
10 conflicts
0xf7ae2120…d1d2
0x34b655…2a6f
10 touches
10 conflicts
0xfcc8f826…7c5f
0x34b655…2a6f
8 touches
6 conflicts
0x25445267…a756
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
10 conflicts on slot 0xba1edffb42…64323e
Audit this contract →
← previous block·next block →recent activity