← previous blocknext block →recent activity
Analyzing
Block #86,960,625
20 transactions · 19 stateful · 2026-07-11 02:04:31 UTC
Parallelism
85/100
Blocked
37%
Avg conflicts / tx
0.5
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #86,960,625 · 20 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
1w03w04w18w09w110w211w113w215w118w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0733be30…112f
0x34b655…2a6f
6 touches
3 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
6 touches
3 conflicts
0x16a8cd0c…27bd
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0x8a35acfb…d1a7
0xb1dbf0…c0d3
4 touches
1 conflict
0xbbcfef8e…8760
0x065c9d…c394
4 touches
1 conflict
0x0363d65e…06d2
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
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
3 conflicts on slot 0x0733be30d6…38112f
Audit this contract →
← previous block·next block →recent activity