← previous blocknext block →recent activity
Analyzing
Block #86,669,585
23 transactions · 21 stateful · 2026-07-09 17:39:47 UTC
Parallelism
91/100
Blocked
10%
Avg conflicts / tx
0.09
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #86,669,585 · 23 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
5w013w120w021w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6278b1b2…ba7b
0x34b655…2a6f
4 touches
1 conflict
0x986aef26…72c2
0x065c9d…c394
4 touches
1 conflict
0x7d42dc8b…fdb6
0x2a68ba…90c5
4 touches
1 conflict
0xa1087a5c…66c4
0x754704…b603
4 touches
1 conflict
0x18aed20c…48f3
0x000000…012a
2 touches
0 conflicts
0x4245e4e8…096e
0x000000…012a
2 touches
0 conflicts
0x7b43f938…3650
0x000000…012a
2 touches
0 conflicts
0x4dd1db39…a994
0x188d58…ea8e
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
1 conflict on slot 0x6278b1b2cf…34ba7b
Audit this contract →
← previous block·next block →recent activity