← previous blocknext block →recent activity
Analyzing
Block #105,929,400
28 transactions · 27 stateful · 2026-09-18 15:41:34 UTC
Parallelism
82/100
Blocked
26%
Avg conflicts / tx
0.46
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #105,929,400 · 28 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w04w07w111w012w115w116w217w318w426w027w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xdb11940a…519b
0x34b655…2a6f
8 touches
6 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xf90c6521…d8f0
0x34b655…2a6f
6 touches
3 conflicts
0x4265984a…a7d2
0x34b655…2a6f
4 touches
1 conflict
0x51fc8795…1266
0x34b655…2a6f
4 touches
1 conflict
0x75c1cb2e…01dd
0x34b655…2a6f
4 touches
1 conflict
0x7792057a…be9c
0x34b655…2a6f
4 touches
1 conflict
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
6 conflicts on slot 0xdb11940a1f…24519b
Audit this contract →
← previous block·next block →recent activity