← previous blocknext block →recent activity
Analyzing
Block #105,932,011
16 transactions · 16 stateful · 2026-09-18 15:54:43 UTC
Parallelism
88/100
Blocked
13%
Avg conflicts / tx
0.13
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #105,932,011 · 16 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w04w111w012w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x14690632…e9a5
0x34b655…2a6f
4 touches
1 conflict
0xd17580f9…ece1
0x754704…b603
4 touches
1 conflict
0xda18212c…b8b6
0x34b655…2a6f
4 touches
1 conflict
0x463e1e6b…87b5
0x34b655…2a6f
3 touches
1 conflict
0x09fd67df…c73c
0x34b655…2a6f
2 touches
0 conflicts
0x04d4f30d…4dfb
0x34b655…2a6f
2 touches
0 conflicts
0x16be5f21…c5a8
0x34b655…2a6f
2 touches
0 conflicts
0x173b64af…6c43
0x34b655…2a6f
2 touches
0 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
1 conflict on slot 0x14690632c8…13e9a5
Audit this contract →
← previous block·next block →recent activity