← previous blocknext block →recent activity
Analyzing
Block #106,932,404
22 transactions · 21 stateful · 2026-09-22 03:50:50 UTC
Parallelism
68/100
Blocked
48%
Avg conflicts / tx
0.95
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #106,932,404 · 22 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w04w16w07w18w29w310w411w512w615w216w320w021w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd1b40f29…9b9d
0x34b655…2a6f
12 touches
15 conflicts
0xe720a4c6…8eb0
0x34b655…2a6f
10 touches
10 conflicts
0xb7aa9720…56df
0x34b655…2a6f
10 touches
10 conflicts
0x9375a764…dca1
0x34b655…2a6f
6 touches
3 conflicts
0x6cad301f…15b7
0x34b655…2a6f
4 touches
1 conflict
0x42522e76…2592
0x34b655…2a6f
4 touches
1 conflict
0x503df629…59cb
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4aa
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 0xd1b40f2924…ae9b9d
Audit this contract →
← previous block·next block →recent activity