← previous blocknext block →recent activity
Analyzing
Block #106,155,905
42 transactions · 23 stateful · 2026-09-19 10:41:40 UTC
Parallelism
88/100
Blocked
43%
Avg conflicts / tx
0.4
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #106,155,905 · 42 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
4w06w08w113w019w224w125w226w334w035w136w237w238w440w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x65903ef9…2567
0x34b655…2a6f
10 touches
10 conflicts
0xea02471d…1542
0x34b655…2a6f
10 touches
10 conflicts
0x3643741b…109c
0x34b655…2a6f
8 touches
6 conflicts
0x366a19b0…f065
0x34b655…2a6f
8 touches
6 conflicts
0x612b5b5d…78b9
0x34b655…2a6f
8 touches
6 conflicts
0x68292fe7…d918
0x34b655…2a6f
8 touches
6 conflicts
0x9fff3d04…b5fd
0x34b655…2a6f
8 touches
6 conflicts
0xa3ff1ab2…8ae3
0x34b655…2a6f
8 touches
6 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 0x65903ef9a0…7d2567
Audit this contract →
← previous block·next block →recent activity