← previous blocknext block →recent activity
Analyzing
Block #106,469,653
22 transactions · 21 stateful · 2026-09-20 13:00:46 UTC
Parallelism
68/100
Blocked
43%
Avg conflicts / tx
0.77
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #106,469,653 · 22 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
2w03w14w15w27w38w09w015w416w518w119w120w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe0d9ed00…4e8d
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0xa3ed5a09…c6d3
0x34b655…2a6f
6 touches
3 conflicts
0x524f0872…0d12
0x34b655…2a6f
6 touches
3 conflicts
0x49b9fdd5…9c16
0x34b655…2a6f
4 touches
1 conflict
0x5655f5c3…6b75
0x34b655…2a6f
4 touches
1 conflict
0x94e7f277…471b
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
6 conflicts on slot 0xe0d9ed0076…884e8d
Audit this contract →
← previous block·next block →recent activity