← previous blocknext block →recent activity
Analyzing
Block #106,957,551
20 transactions · 19 stateful · 2026-09-22 05:57:25 UTC
Parallelism
65/100
Blocked
53%
Avg conflicts / tx
1.75
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #106,957,551 · 20 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
1w02w17w08w19w210w312w214w415w516w517w619w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb9961fb2…18e5
0x34b655…2a6f
14 touches
21 conflicts
0x52b0b60a…f21e
0x34b655…2a6f
14 touches
21 conflicts
0xc824469a…6425
0x34b655…2a6f
14 touches
21 conflicts
0x858e40c0…7e30
0x34b655…2a6f
12 touches
15 conflicts
0xd1b40f29…9b9d
0x34b655…2a6f
10 touches
10 conflicts
0xe22ab637…7a8e
0x34b655…2a6f
8 touches
6 conflicts
0x8d5fc820…1750
0x34b655…2a6f
6 touches
3 conflicts
0xa9ba0084…9600
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
21 conflicts on slot 0xb9961fb2ca…7b18e5
Audit this contract →
← previous block·next block →recent activity