← previous blocknext block →recent activity
Analyzing
Block #106,921,496
20 transactions · 19 stateful · 2026-09-22 02:55:56 UTC
Parallelism
60/100
Blocked
37%
Avg conflicts / tx
1
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #106,921,496 · 20 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
7w08w19w211w312w413w514w615w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x206f4379…e08a
0x34b655…2a6f
12 touches
15 conflicts
0x799c3770…96ae
0x34b655…2a6f
10 touches
10 conflicts
0xccebf5c5…8758
0x34b655…2a6f
10 touches
10 conflicts
0xab981df1…2941
0x34b655…2a6f
8 touches
6 conflicts
0xa66499c2…9f47
0x34b655…2a6f
6 touches
3 conflicts
0x49890ced…6f23
0x34b655…2a6f
6 touches
3 conflicts
0xe4a10d60…841b
0x34b655…2a6f
4 touches
1 conflict
0x01a89030…f786
0x98dc6e…8633
2 touches
0 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
15 conflicts on slot 0x206f43799d…55e08a
Audit this contract →
← previous block·next block →recent activity