← previous blocknext block →recent activity
Analyzing
Block #106,542,250
27 transactions · 26 stateful · 2026-09-20 19:06:09 UTC
Parallelism
74/100
Blocked
35%
Avg conflicts / tx
1.11
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #106,542,250 · 27 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w25w36w412w525w526w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbc8fb280…76a3
0x34b655…2a6f
14 touches
21 conflicts
0xd9301867…5814
0x34b655…2a6f
12 touches
15 conflicts
0xca841faa…486a
0x34b655…2a6f
12 touches
15 conflicts
0x4ae38164…15f0
0x34b655…2a6f
10 touches
10 conflicts
0x5ad5e6de…e7ad
0x34b655…2a6f
10 touches
10 conflicts
0x656c2ba5…d35b
0x34b655…2a6f
10 touches
10 conflicts
0x90b49c59…4807
0x34b655…2a6f
10 touches
10 conflicts
0xa7d3cb90…e1d9
0x34b655…2a6f
10 touches
10 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
21 conflicts on slot 0xbc8fb28081…2176a3
Audit this contract →
← previous block·next block →recent activity