← previous blocknext block →recent activity
Analyzing
Block #106,567,660
11 transactions · 11 stateful · 2026-09-20 21:14:01 UTC
Parallelism
82/100
Blocked
9%
Avg conflicts / tx
0.09
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #106,567,660 · 11 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
6w07w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xba1edffb…323e
0x34b655…2a6f
4 touches
1 conflict
0x5d1ac445…5233
0x34b655…2a6f
4 touches
1 conflict
0x14e6dc74…6e3b
0x34b655…2a6f
4 touches
1 conflict
0xad99b1fd…1c5a
0x34b655…2a6f
4 touches
1 conflict
0xaad6be10…0801
0x2a68ba…90c5
2 touches
0 conflicts
0x0949e4a6…8f2f
0x34b655…2a6f
2 touches
0 conflicts
0x0de7749d…5bef
0x34b655…2a6f
2 touches
0 conflicts
0x17bb579f…938c
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 0xba1edffb42…64323e
Audit this contract →
← previous block·next block →recent activity