← previous blocknext block →recent activity
Analyzing
Block #105,851,679
32 transactions · 32 stateful · 2026-09-18 09:09:31 UTC
Parallelism
72/100
Blocked
66%
Avg conflicts / tx
2.03
Longest chain
9 deep
Execution timeline
did this block parallelize well?
view
block #105,851,679 · 32 txs across 9 waves · depth 9
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w07w18w210w211w112w213w314w415w516w617w718w820w331w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x382434ca…96b5
0x34b655…2a6f
18 touches
36 conflicts
0x34fe25fc…0293
0x34b655…2a6f
14 touches
21 conflicts
0x0efc210e…70ab
0x34b655…2a6f
10 touches
10 conflicts
0xd17580f9…ece1
0x754704…b603
10 touches
10 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0x81ca8c9e…28cb
0x34b655…2a6f
8 touches
6 conflicts
0x42522e76…2592
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
36 conflicts on slot 0x382434ca57…4d96b5
Audit this contract →
← previous block·next block →recent activity