← previous blocknext block →recent activity
Analyzing
Block #105,461,552
14 transactions · 14 stateful · 2026-09-17 00:24:33 UTC
Parallelism
79/100
Blocked
29%
Avg conflicts / tx
0.57
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #105,461,552 · 14 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w04w16w07w110w212w013w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0c0f4ae9…4da1
0x34b655…2a6f
6 touches
3 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x9c2fc330…0091
0x34b655…2a6f
4 touches
1 conflict
0xa90eb29b…2cec
0x34b655…2a6f
4 touches
1 conflict
0xc10b903d…2f54
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x00000000…0028
0x1b6862…e19c
2 touches
0 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
3 conflicts on slot 0x0c0f4ae99e…f34da1
Audit this contract →
← previous block·next block →recent activity