← previous blocknext block →recent activity
Analyzing
Block #105,626,211
28 transactions · 27 stateful · 2026-09-17 14:13:17 UTC
Parallelism
79/100
Blocked
59%
Avg conflicts / tx
1.32
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #105,626,211 · 28 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w28w09w110w211w312w414w217w518w119w220w321w322w423w524w327w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd1448207…452d
0x34b655…2a6f
10 touches
10 conflicts
0xa7ecbbe7…f713
0x34b655…2a6f
10 touches
10 conflicts
0xca841faa…486a
0x34b655…2a6f
8 touches
6 conflicts
0x9a562fab…1a9a
0x34b655…2a6f
8 touches
6 conflicts
0x4d358ff7…e219
0x34b655…2a6f
8 touches
6 conflicts
0x7c51d9aa…af39
0x34b655…2a6f
8 touches
6 conflicts
0x0efc210e…70ab
0x34b655…2a6f
8 touches
6 conflicts
0x42522e76…2592
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
10 conflicts on slot 0xd144820738…06452d
Audit this contract →
← previous block·next block →recent activity