← previous blocknext block →recent activity
Analyzing
Block #106,810,377
16 transactions · 16 stateful · 2026-09-21 17:36:37 UTC
Parallelism
75/100
Blocked
38%
Avg conflicts / tx
0.81
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #106,810,377 · 16 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w05w17w19w010w111w212w313w015w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbe4dbfb0…c43c
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xf2ed177c…74be
0x34b655…2a6f
6 touches
3 conflicts
0xf96ce57c…78bb
0x34b655…2a6f
6 touches
3 conflicts
0x05e1eba1…6491
0x34b655…2a6f
6 touches
3 conflicts
0x6c26d635…1bbf
0x34b655…2a6f
4 touches
1 conflict
0x6d1b72ee…6b78
0x34b655…2a6f
4 touches
1 conflict
0x01f19c33…170d
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
6 conflicts on slot 0xbe4dbfb032…b6c43c
Audit this contract →
← previous block·next block →recent activity