← previous blocknext block →recent activity
Analyzing
Block #85,522,909
32 transactions · 24 stateful · 2026-07-04 10:04:55 UTC
Parallelism
81/100
Blocked
33%
Avg conflicts / tx
0.63
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #85,522,909 · 32 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
1w04w110w011w113w215w017w023w124w025w227w029w330w431w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
10 touches
10 conflicts
0xa7396f51…7f2f
0x34b655…2a6f
6 touches
3 conflicts
0xd84ac41a…4ceb
0x34b655…2a6f
6 touches
3 conflicts
0xfaef08b1…0696
0x34b655…2a6f
6 touches
3 conflicts
0x3923cd2c…e6d3
0x34b655…2a6f
4 touches
1 conflict
0x6f2fcf68…a665
0x34b655…2a6f
4 touches
1 conflict
0x9092da13…341b
0x34b655…2a6f
4 touches
1 conflict
0xa20a130c…5d59
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
10 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity