← previous blocknext block →recent activity
Analyzing
Block #106,916,306
18 transactions · 18 stateful · 2026-09-22 02:29:49 UTC
Parallelism
72/100
Blocked
50%
Avg conflicts / tx
0.89
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #106,916,306 · 18 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
3w04w15w06w17w28w09w110w211w312w414w117w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x825865a0…b736
0x34b655…2a6f
10 touches
10 conflicts
0xccebf5c5…8758
0x34b655…2a6f
10 touches
10 conflicts
0x69411fb3…e36d
0x34b655…2a6f
10 touches
10 conflicts
0x574628e9…dcc3
0x34b655…2a6f
6 touches
3 conflicts
0x49890ced…6f23
0x34b655…2a6f
6 touches
3 conflicts
0xfc906557…ae7f
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x865ea77d…3eea
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
10 conflicts on slot 0x825865a08e…44b736
Audit this contract →
← previous block·next block →recent activity