← previous blocknext block →recent activity
Analyzing
Block #105,843,463
22 transactions · 20 stateful · 2026-09-18 08:28:07 UTC
Parallelism
64/100
Blocked
45%
Avg conflicts / tx
1.68
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #105,843,463 · 22 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
2w04w07w010w111w212w313w414w515w616w721w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa8ec9a76…0e02
0x34b655…2a6f
16 touches
28 conflicts
0xfd7f5b55…4994
0x34b655…2a6f
12 touches
15 conflicts
0xfca8addf…4b41
0x34b655…2a6f
12 touches
15 conflicts
0xa8590d68…d5c8
0x34b655…2a6f
10 touches
10 conflicts
0x6d955786…1327
0x34b655…2a6f
10 touches
10 conflicts
0x5e3014f0…b4e1
0x34b655…2a6f
10 touches
10 conflicts
0x66e2f9ee…306e
0x34b655…2a6f
6 touches
3 conflicts
0x6fbc2e5a…e69c
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 0xa8ec9a769c…e20e02
Audit this contract →
← previous block·next block →recent activity