← previous blocknext block →recent activity
Analyzing
Block #106,413,836
20 transactions · 18 stateful · 2026-09-20 08:19:48 UTC
Parallelism
60/100
Blocked
50%
Avg conflicts / tx
1.4
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #106,413,836 · 20 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w05w110w211w312w413w414w515w616w617w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfdd131fa…dbdb
0x34b655…2a6f
10 touches
10 conflicts
0xc20bb2f9…b221
0x34b655…2a6f
8 touches
6 conflicts
0xca841faa…486a
0x34b655…2a6f
8 touches
6 conflicts
0x524f0872…0d12
0x34b655…2a6f
8 touches
6 conflicts
0xa8531704…5a2e
0x34b655…2a6f
8 touches
6 conflicts
0x55a7c54b…bdcc
0x34b655…2a6f
8 touches
6 conflicts
0x550e12cc…8985
0x34b655…2a6f
7 touches
6 conflicts
0x9a9383a9…6bc7
0x34b655…2a6f
6 touches
3 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
10 conflicts on slot 0xfdd131fae1…f8dbdb
Audit this contract →
← previous block·next block →recent activity