← previous blocknext block →recent activity
Analyzing
Block #105,857,600
18 transactions · 18 stateful · 2026-09-18 09:39:19 UTC
Parallelism
56/100
Blocked
50%
Avg conflicts / tx
1.72
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #105,857,600 · 18 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w15w110w211w212w313w414w515w616w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfc72374d…7ffd
0x34b655…2a6f
14 touches
21 conflicts
0x8db32935…81a7
0x34b655…2a6f
10 touches
10 conflicts
0xfaf89f45…ced6
0x34b655…2a6f
10 touches
10 conflicts
0xdc2be7c5…60b6
0x34b655…2a6f
10 touches
10 conflicts
0x7c51d9aa…af39
0x34b655…2a6f
6 touches
3 conflicts
0x29cd05f5…390c
0x34b655…2a6f
6 touches
3 conflicts
0x42522e76…2592
0x34b655…2a6f
6 touches
3 conflicts
0x49890ced…6f23
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
21 conflicts on slot 0xfc72374d09…007ffd
Audit this contract →
← previous block·next block →recent activity