← previous blocknext block →recent activity
Analyzing
Block #106,458,235
21 transactions · 18 stateful · 2026-09-20 12:03:19 UTC
Parallelism
71/100
Blocked
61%
Avg conflicts / tx
1
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #106,458,235 · 21 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
1w02w03w14w15w26w27w18w29w315w417w418w520w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x8a02d049…f481
0x34b655…2a6f
10 touches
10 conflicts
0x364036f4…10de
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0x0262e1c6…52e1
0x34b655…2a6f
6 touches
3 conflicts
0xaad6be10…0801
0x2a68ba…90c5
6 touches
3 conflicts
0x94e7f277…471b
0x34b655…2a6f
4 touches
1 conflict
0xa242e227…2e45
0x34b655…2a6f
4 touches
1 conflict
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 0x8a02d04928…c6f481
Audit this contract →
← previous block·next block →recent activity