← previous blocknext block →recent activity
Analyzing
Block #106,577,079
33 transactions · 27 stateful · 2026-09-20 22:01:26 UTC
Parallelism
85/100
Blocked
22%
Avg conflicts / tx
0.48
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #106,577,079 · 33 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w015w016w017w118w119w220w321w429w031w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x2a5dc0db…f558
0x34b655…2a6f
10 touches
10 conflicts
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0xe5eb3c33…0e3a
0x34b655…2a6f
8 touches
6 conflicts
0x110a3804…f842
0x34b655…2a6f
8 touches
6 conflicts
0x588380ee…0a5c
0x34b655…2a6f
6 touches
3 conflicts
0x23b2399c…6e4b
0x34b655…2a6f
4 touches
1 conflict
0x3cf50d44…961b
0x34b655…2a6f
4 touches
1 conflict
0x49b9fdd5…9c16
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
10 conflicts on slot 0x2a5dc0dbab…30f558
Audit this contract →
← previous block·next block →recent activity