← previous blocknext block →recent activity
Analyzing
Block #86,772,281
21 transactions · 18 stateful · 2026-07-10 05:05:41 UTC
Parallelism
76/100
Blocked
44%
Avg conflicts / tx
0.76
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #86,772,281 · 21 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
1w03w04w17w08w19w210w313w014w216w317w120w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x3a6290da…e683
0x34b655…2a6f
8 touches
6 conflicts
0xfaef08b1…0696
0x34b655…2a6f
8 touches
6 conflicts
0x2c8bf7d9…3cc7
0xc8689a…ee79
6 touches
3 conflicts
0xcf17589f…048c
0x34b655…2a6f
6 touches
3 conflicts
0xdd7aabe0…0f0d
0x34b655…2a6f
6 touches
3 conflicts
0xee75c266…f8c6
0x34b655…2a6f
6 touches
3 conflicts
0xee90ddc0…e4e8
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…003d
0xa6afd3…d132
6 touches
3 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
6 conflicts on slot 0x3a6290da4d…93e683
Audit this contract →
← previous block·next block →recent activity