← previous blocknext block →recent activity
Analyzing
Block #106,552,240
28 transactions · 27 stateful · 2026-09-20 19:56:25 UTC
Parallelism
64/100
Blocked
59%
Avg conflicts / tx
1.93
Longest chain
10 deep
Execution timeline
did this block parallelize well?
view
block #106,552,240 · 28 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
1w02w18w110w213w315w216w417w518w619w720w821w9
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x18544555…38e9
0x34b655…2a6f
16 touches
28 conflicts
0x3ebaf0ea…87c4
0x34b655…2a6f
16 touches
28 conflicts
0xd62f3741…b903
0x34b655…2a6f
14 touches
21 conflicts
0x46483cb1…e7ca
0x34b655…2a6f
12 touches
15 conflicts
0x524f0872…0d12
0x34b655…2a6f
10 touches
10 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0x51fc8795…126f
0x34b655…2a6f
8 touches
6 conflicts
0x7dd96c96…7335
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
28 conflicts on slot 0x185445552e…d938e9
Audit this contract →
← previous block·next block →recent activity