← previous blocknext block →recent activity
Analyzing
Block #105,855,307
21 transactions · 20 stateful · 2026-09-18 09:27:46 UTC
Parallelism
71/100
Blocked
40%
Avg conflicts / tx
0.86
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #105,855,307 · 21 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
1w02w14w07w111w212w313w414w515w016w119w020w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x9dccd2a9…2790
0x34b655…2a6f
12 touches
15 conflicts
0x9c10e452…fbef
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0x0efc210e…70ab
0x34b655…2a6f
8 touches
6 conflicts
0x3e6a1486…a9fb
0x34b655…2a6f
6 touches
3 conflicts
0x7c51d9aa…af39
0x34b655…2a6f
6 touches
3 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
4 touches
1 conflict
0x42522e76…2592
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 0x9dccd2a98b…6d2790
Audit this contract →
← previous block·next block →recent activity