← previous blocknext block →recent activity
Analyzing
Block #105,618,657
35 transactions · 35 stateful · 2026-09-17 13:35:15 UTC
Parallelism
51/100
Blocked
66%
Avg conflicts / tx
2.09
Longest chain
17 deep
Execution timeline
did this block parallelize well?
view
block #105,618,657 · 35 txs across 17 waves · depth 17
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
wave w11
wave w12
wave w13
wave w14
wave w15
wave w16
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w04w15w26w38w09w111w212w013w114w215w316w417w518w624w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
18 touches
36 conflicts
0xca841faa…486a
0x34b655…2a6f
14 touches
21 conflicts
0x1fb8364c…c10d
0x34b655…2a6f
12 touches
15 conflicts
0x22badbc6…4c24
0x34b655…2a6f
12 touches
15 conflicts
0x5f76b8ee…ecfe
0x34b655…2a6f
12 touches
15 conflicts
0x6d5d1fb5…86a7
0x34b655…2a6f
12 touches
15 conflicts
0x75f36d60…8556
0x34b655…2a6f
12 touches
15 conflicts
0x8b7e5c4e…5fae
0x34b655…2a6f
12 touches
15 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 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity