← previous blocknext block →recent activity
Analyzing
Block #105,848,896
35 transactions · 33 stateful · 2026-09-18 08:55:31 UTC
Parallelism
60/100
Blocked
67%
Avg conflicts / tx
2.77
Longest chain
14 deep
Execution timeline
did this block parallelize well?
view
block #105,848,896 · 35 txs across 14 waves · depth 14
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w46w57w38w213w314w415w522w623w724w825w926w1027w1128w1229w13
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6f2bac24…cab4
0x34b655…2a6f
24 touches
66 conflicts
0x7cfb984a…4d58
0x34b655…2a6f
18 touches
36 conflicts
0x97e4c862…4419
0x34b655…2a6f
14 touches
21 conflicts
0xc824469a…6425
0x34b655…2a6f
14 touches
21 conflicts
0x4118bd12…924a
0x34b655…2a6f
12 touches
15 conflicts
0x7c51d9aa…af39
0x34b655…2a6f
12 touches
15 conflicts
0xbe66a678…1af7
0xd32edf…ff58
11 touches
15 conflicts
0x00000000…0012
0x1b6862…e19c
10 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
66 conflicts on slot 0x6f2bac24f3…eccab4
Audit this contract →
← previous block·next block →recent activity