← previous blocknext block →recent activity
Analyzing
Block #106,801,618
23 transactions · 20 stateful · 2026-09-21 16:52:32 UTC
Parallelism
70/100
Blocked
55%
Avg conflicts / tx
1.3
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #106,801,618 · 23 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w15w19w210w311w012w215w416w117w518w221w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x38594928…2c55
0x34b655…2a6f
10 touches
10 conflicts
0x77ca8ee1…e3db
0x34b655…2a6f
10 touches
10 conflicts
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0xbd9491f7…dd92
0x34b655…2a6f
6 touches
3 conflicts
0xf2f76ab3…623e
0x2a68ba…90c5
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…003d
0x40c49f…2af0
4 touches
1 conflict
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 0x385949288b…662c55
Audit this contract →
← previous block·next block →recent activity