← previous blocknext block →recent activity
Analyzing
Block #106,953,793
22 transactions · 21 stateful · 2026-09-22 05:38:30 UTC
Parallelism
64/100
Blocked
43%
Avg conflicts / tx
1.05
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #106,953,793 · 22 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w06w18w29w311w212w016w417w519w120w621w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd4664554…531d
0x34b655…2a6f
12 touches
15 conflicts
0xef5959a3…2a2f
0x34b655…2a6f
8 touches
6 conflicts
0xc953c572…34b1
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0x53ca1284…cb2c
0x34b655…2a6f
6 touches
3 conflicts
0xba5743c7…21c4
0x1b6862…e19c
4 touches
1 conflict
0xd9f18d9a…141d
0x1b6862…e19c
4 touches
1 conflict
0x94e7f277…471b
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 0xd46645541f…bb531d
Audit this contract →
← previous block·next block →recent activity