← previous blocknext block →recent activity
Analyzing
Block #106,945,074
33 transactions · 32 stateful · 2026-09-22 04:54:37 UTC
Parallelism
79/100
Blocked
44%
Avg conflicts / tx
1.12
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #106,945,074 · 33 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
2w03w14w05w07w08w111w015w016w117w218w119w220w321w322w426w127w528w631w132w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xdb4c0eb3…f7b9
0x34b655…2a6f
14 touches
21 conflicts
0xea79e6d3…68ad
0x34b655…2a6f
12 touches
15 conflicts
0xfaf89f45…ced6
0x34b655…2a6f
8 touches
6 conflicts
0x49890ced…6f23
0x34b655…2a6f
6 touches
3 conflicts
0x8dad7932…7029
0x34b655…2a6f
6 touches
3 conflicts
0x94dabb65…43a3
0x34b655…2a6f
6 touches
3 conflicts
0x51087f5a…61f7
0x34b655…2a6f
6 touches
3 conflicts
0xcb21158b…f18d
0x34b655…2a6f
6 touches
3 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 0xdb4c0eb325…adf7b9
Audit this contract →
← previous block·next block →recent activity