← previous blocknext block →recent activity
Analyzing
Block #106,197,706
22 transactions · 21 stateful · 2026-09-19 14:12:02 UTC
Parallelism
59/100
Blocked
57%
Avg conflicts / tx
1.68
Longest chain
9 deep
Execution timeline
did this block parallelize well?
view
block #106,197,706 · 22 txs across 9 waves · depth 9
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w05w17w29w213w316w317w418w519w620w721w8
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x616e6caa…e369
0x34b655…2a6f
14 touches
21 conflicts
0x5655f5c3…6b75
0x34b655…2a6f
12 touches
15 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0xd66696e0…0842
0x34b655…2a6f
6 touches
3 conflicts
0xb550abea…2729
0x34b655…2a6f
6 touches
3 conflicts
0x76ed8777…1e5f
0x34b655…2a6f
6 touches
3 conflicts
0xe22ab637…7a8e
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 0x616e6caab9…d3e369
Audit this contract →
← previous block·next block →recent activity