← previous blocknext block →recent activity
Analyzing
Block #106,453,927
21 transactions · 20 stateful · 2026-09-20 11:41:38 UTC
Parallelism
52/100
Blocked
55%
Avg conflicts / tx
2.14
Longest chain
10 deep
Execution timeline
did this block parallelize well?
view
block #106,453,927 · 21 txs across 10 waves · depth 10
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w07w18w19w210w311w412w513w514w615w716w817w9
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5e2ea201…12de
0x34b655…2a6f
14 touches
21 conflicts
0xa4154323…6854
0x34b655…2a6f
10 touches
10 conflicts
0xc0a692d1…0ef8
0x34b655…2a6f
10 touches
10 conflicts
0x1cdfe548…d3aa
0x34b655…2a6f
8 touches
6 conflicts
0x31e47e6c…87f9
0x34b655…2a6f
8 touches
6 conflicts
0x89eaf36a…4e48
0x34b655…2a6f
8 touches
6 conflicts
0xa3ed5a09…c6d3
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 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 0x5e2ea201dc…2012de
Audit this contract →
← previous block·next block →recent activity