← previous blocknext block →recent activity
Analyzing
Block #86,741,360
17 transactions · 16 stateful · 2026-07-10 01:39:04 UTC
Parallelism
76/100
Blocked
38%
Avg conflicts / tx
0.76
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #86,741,360 · 17 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w26w08w110w311w113w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x636fd21a…9978
0x34b655…2a6f
8 touches
6 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
8 touches
6 conflicts
0x157dbfb2…4089
0x34b655…2a6f
6 touches
3 conflicts
0x321eac33…6aca
0x34b655…2a6f
6 touches
3 conflicts
0x398b64f7…4b55
0x34b655…2a6f
6 touches
3 conflicts
0x41a19c97…4d3f
0x34b655…2a6f
6 touches
3 conflicts
0x427f51fd…bd80
0x34b655…2a6f
6 touches
3 conflicts
0x5261c6c4…007f
0x34b655…2a6f
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 0x636fd21a61…849978
Audit this contract →
← previous block·next block →recent activity