← previous blocknext block →recent activity
Analyzing
Block #105,633,894
31 transactions · 30 stateful · 2026-09-17 14:51:58 UTC
Parallelism
68/100
Blocked
70%
Avg conflicts / tx
1.77
Longest chain
10 deep
Execution timeline
did this block parallelize well?
view
block #105,633,894 · 31 txs across 10 waves · depth 10
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w25w36w47w08w19w310w113w317w218w419w524w625w726w827w930w9
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb35cc273…97dc
0x34b655…2a6f
16 touches
28 conflicts
0x6ca0994e…02ef
0x34b655…2a6f
10 touches
10 conflicts
0x51fc8795…126f
0x34b655…2a6f
8 touches
6 conflicts
0x0463db49…5d05
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…002b
0x1b6862…e19c
6 touches
3 conflicts
0xb0e4f69d…34e4
0x1b6862…e19c
6 touches
3 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
6 touches
3 conflicts
0x14690632…e9a5
0x34b655…2a6f
6 touches
3 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
28 conflicts on slot 0xb35cc273f1…e497dc
Audit this contract →
← previous block·next block →recent activity