← previous blocknext block →recent activity
Analyzing
Block #105,841,170
35 transactions · 33 stateful · 2026-09-18 08:16:29 UTC
Parallelism
80/100
Blocked
58%
Avg conflicts / tx
1.31
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #105,841,170 · 35 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
1w02w13w26w211w012w113w014w115w216w317w422w324w325w426w527w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe9c367cd…30a9
0x34b655…2a6f
14 touches
21 conflicts
0x9ff4ca89…6115
0x34b655…2a6f
10 touches
10 conflicts
0x042b8481…b5aa
0x6f6493…b480
9 touches
10 conflicts
0x07b057b2…612d
0x6f6493…b480
9 touches
10 conflicts
0x12892f72…262f
0x6f6493…b480
9 touches
10 conflicts
0x165dcf2f…44af
0x6f6493…b480
9 touches
10 conflicts
0x1b526838…240e
0x6f6493…b480
9 touches
10 conflicts
0x1c2e736b…0178
0x6f6493…b480
9 touches
10 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
21 conflicts on slot 0xe9c367cd5c…aa30a9
Audit this contract →
← previous block·next block →recent activity