← previous blocknext block →recent activity
Analyzing
Block #106,423,942
23 transactions · 22 stateful · 2026-09-20 09:10:40 UTC
Parallelism
65/100
Blocked
50%
Avg conflicts / tx
1.78
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #106,423,942 · 23 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w15w07w210w312w313w414w515w117w418w519w620w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x60be5cbc…7218
0x34b655…2a6f
14 touches
21 conflicts
0xbe9d1d23…3de2
0x34b655…2a6f
10 touches
10 conflicts
0x000bde1a…e123
0x34b655…2a6f
10 touches
10 conflicts
0x53ca1284…cb2c
0x34b655…2a6f
8 touches
6 conflicts
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0xc5184473…3d1a
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0x2c2db8e9…fdc7
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 0x60be5cbc32…9f7218
Audit this contract →
← previous block·next block →recent activity