← previous blocknext block →recent activity
Analyzing
Block #106,537,520
24 transactions · 23 stateful · 2026-09-20 18:42:21 UTC
Parallelism
75/100
Blocked
61%
Avg conflicts / tx
1.5
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #106,537,520 · 24 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w14w25w08w09w111w112w214w215w316w319w220w421w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe098738f…9bbe
0x34b655…2a6f
8 touches
6 conflicts
0x172b0de5…980b
0x34b655…2a6f
8 touches
6 conflicts
0x1b25f260…c429
0x34b655…2a6f
8 touches
6 conflicts
0x2043808e…8861
0x34b655…2a6f
8 touches
6 conflicts
0x2d071de0…c86e
0x34b655…2a6f
8 touches
6 conflicts
0x49b9fdd5…9c16
0x34b655…2a6f
8 touches
6 conflicts
0x69411fb3…e36d
0x34b655…2a6f
8 touches
6 conflicts
0x7e2ddb96…2285
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
6 conflicts on slot 0xe098738f16…fd9bbe
Audit this contract →
← previous block·next block →recent activity