← previous blocknext block →recent activity
Analyzing
Block #105,870,164
31 transactions · 31 stateful · 2026-09-18 10:42:33 UTC
Parallelism
52/100
Blocked
61%
Avg conflicts / tx
3.74
Longest chain
15 deep
Execution timeline
did this block parallelize well?
view
block #105,870,164 · 31 txs across 15 waves · depth 15
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w05w08w19w212w213w114w315w416w517w618w719w821w922w1023w1124w1225w1326w1429w230w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
24 touches
66 conflicts
0x9dccd2a9…2790
0x34b655…2a6f
18 touches
36 conflicts
0x9c83a7b1…e305
0x34b655…2a6f
14 touches
21 conflicts
0x42d8f3e4…4199
0x34b655…2a6f
14 touches
21 conflicts
0x49890ced…6f23
0x34b655…2a6f
14 touches
21 conflicts
0xdef81c0c…4eb5
0x34b655…2a6f
14 touches
21 conflicts
0xd79c9727…1233
0x34b655…2a6f
12 touches
15 conflicts
0x42522e76…2592
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
66 conflicts on slot 0xc824469a90…af6425
Audit this contract →
← previous block·next block →recent activity