← previous blocknext block →recent activity
Analyzing
Block #105,845,501
27 transactions · 24 stateful · 2026-09-18 08:38:26 UTC
Parallelism
78/100
Blocked
54%
Avg conflicts / tx
1.22
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #105,845,501 · 27 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w16w08w19w012w113w214w315w416w517w018w119w220w321w422w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x904bb1d5…0100
0x34b655…2a6f
12 touches
15 conflicts
0xd17580f9…ece1
0x754704…b603
12 touches
15 conflicts
0xa6d40b7f…2969
0x34b655…2a6f
10 touches
10 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0xeee61405…7284
0x34b655…2a6f
8 touches
6 conflicts
0x941bd594…21fd
0x34b655…2a6f
6 touches
3 conflicts
0x80398c66…f3cc
0x34b655…2a6f
6 touches
3 conflicts
0x80bc3112…747d
0x34b655…2a6f
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
15 conflicts on slot 0x904bb1d5f9…da0100
Audit this contract →
← previous block·next block →recent activity