← previous blocknext block →recent activity
Analyzing
Block #105,880,323
17 transactions · 17 stateful · 2026-09-18 11:33:40 UTC
Parallelism
71/100
Blocked
53%
Avg conflicts / tx
1.29
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #105,880,323 · 17 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
1w02w16w07w08w29w110w111w212w313w415w116w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x297de2d5…7396
0x34b655…2a6f
10 touches
10 conflicts
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0xcb334a17…b16e
0x34b655…2a6f
8 touches
6 conflicts
0x4e1bba0c…d8ba
0x34b655…2a6f
8 touches
6 conflicts
0x5b6af007…0f35
0x34b655…2a6f
6 touches
3 conflicts
0xb75367ff…a2b7
0x34b655…2a6f
6 touches
3 conflicts
0x51fc8795…126f
0x34b655…2a6f
6 touches
3 conflicts
0x206f4379…e08a
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 0x297de2d577…2b7396
Audit this contract →
← previous block·next block →recent activity