← previous blocknext block →recent activity
Analyzing
Block #106,916,586
20 transactions · 17 stateful · 2026-09-22 02:31:13 UTC
Parallelism
75/100
Blocked
35%
Avg conflicts / tx
0.65
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #106,916,586 · 20 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
1w02w14w06w19w211w313w415w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xca841faa…486a
0x34b655…2a6f
10 touches
10 conflicts
0x8514b614…35a9
0xa6afd3…d132
6 touches
3 conflicts
0x00000000…003d
0xa6afd3…d132
6 touches
3 conflicts
0x0c17a749…8012
0x34b655…2a6f
4 touches
1 conflict
0x26744466…9f4c
0x34b655…2a6f
4 touches
1 conflict
0x46cbc06b…eb46
0x34b655…2a6f
4 touches
1 conflict
0x573e497e…dab5
0x34b655…2a6f
4 touches
1 conflict
0x98a1bad6…5130
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 0xca841faae5…71486a
Audit this contract →
← previous block·next block →recent activity