← previous blocknext block →recent activity
Analyzing
Block #106,382,152
13 transactions · 13 stateful · 2026-09-20 05:40:21 UTC
Parallelism
77/100
Blocked
23%
Avg conflicts / tx
0.23
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #106,382,152 · 13 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w07w110w211w012w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xba33378a…f1df
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xe863a525…58c2
0x5be4ee…673f
3 touches
1 conflict
0xe863a525…58d0
0x5be4ee…673f
3 touches
1 conflict
0x2573d0ca…d0b5
0x34b655…2a6f
2 touches
0 conflicts
0x282d0473…a801
0x34b655…2a6f
2 touches
0 conflicts
0x2c2db8e9…fdc7
0x34b655…2a6f
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
1 conflict on slot 0xba33378abc…73f1df
Audit this contract →
← previous block·next block →recent activity