← previous blocknext block →recent activity
Analyzing
Block #106,420,582
15 transactions · 14 stateful · 2026-09-20 08:53:45 UTC
Parallelism
67/100
Blocked
50%
Avg conflicts / tx
0.87
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #106,420,582 · 15 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
1w02w15w07w18w010w211w312w213w414w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa8d9cec7…043e
0x34b655…2a6f
10 touches
10 conflicts
0x3cd235da…5aed
0x34b655…2a6f
8 touches
6 conflicts
0x310a7246…2dcb
0x34b655…2a6f
6 touches
3 conflicts
0x5e1c23e9…4f81
0x34b655…2a6f
6 touches
3 conflicts
0x80398c66…f3cc
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…002b
0x1b6862…e19c
4 touches
1 conflict
0x69017fce…85be
0x1b6862…e19c
4 touches
1 conflict
0xd9f18d9a…141d
0x1b6862…e19c
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
10 conflicts on slot 0xa8d9cec734…d6043e
Audit this contract →
← previous block·next block →recent activity