← previous blocknext block →recent activity
Analyzing
Block #105,582,767
19 transactions · 16 stateful · 2026-09-17 10:34:34 UTC
Parallelism
68/100
Blocked
44%
Avg conflicts / tx
0.89
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #105,582,767 · 19 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
1w05w19w011w212w313w414w516w017w118w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb528124f…c47d
0x34b655…2a6f
12 touches
15 conflicts
0xcadd9a74…8bb7
0x34b655…2a6f
10 touches
10 conflicts
0x2d3930d3…c9b8
0x34b655…2a6f
8 touches
6 conflicts
0x7b42f6a7…f49c
0x34b655…2a6f
6 touches
3 conflicts
0xe5bb3628…e5f1
0x34b655…2a6f
4 touches
1 conflict
0x09106a95…1467
0x33176b…e078
4 touches
1 conflict
0x1e737223…2278
0x34b655…2a6f
4 touches
1 conflict
0x3d8707da…89d1
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
15 conflicts on slot 0xb528124f63…54c47d
Audit this contract →
← previous block·next block →recent activity