← previous blocknext block →recent activity
Analyzing
Block #106,200,161
29 transactions · 21 stateful · 2026-09-19 14:24:23 UTC
Parallelism
86/100
Blocked
48%
Avg conflicts / tx
0.52
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #106,200,161 · 29 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
1w03w07w08w19w015w116w218w119w220w323w024w125w226w127w028w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x085df2c1…305a
0x34b655…2a6f
8 touches
6 conflicts
0x3643741b…109c
0x34b655…2a6f
8 touches
6 conflicts
0x366a19b0…f065
0x34b655…2a6f
8 touches
6 conflicts
0x68292fe7…d918
0x34b655…2a6f
8 touches
6 conflicts
0x6a9e408e…3721
0x34b655…2a6f
8 touches
6 conflicts
0x74fa9cc0…c570
0x34b655…2a6f
8 touches
6 conflicts
0x839c0c71…bada
0x34b655…2a6f
8 touches
6 conflicts
0x9d3f7d9c…fd83
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 0x085df2c147…d2305a
Audit this contract →
← previous block·next block →recent activity