← previous blocknext block →recent activity
Analyzing
Block #85,189,913
11 transactions · 10 stateful · 2026-07-02 21:07:16 UTC
Parallelism
82/100
Blocked
10%
Avg conflicts / tx
0.18
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #85,189,913 · 11 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
3w04w06w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5e782d17…5318
0x34b655…2a6f
4 touches
1 conflict
0x0efc210e…70ab
0x34b655…2a6f
4 touches
1 conflict
0xf0e3fb87…20a2
0x34b655…2a6f
4 touches
1 conflict
0xc1d2d0e5…3299
0x09475a…400f
2 touches
0 conflicts
0x5cdc8924…c0f1
0x10aeaf…5417
2 touches
0 conflicts
0x482471ad…122f
0x34b655…2a6f
2 touches
0 conflicts
0x4d3a9de0…7c14
0x34b655…2a6f
2 touches
0 conflicts
0x5c0393a4…8b86
0x34b655…2a6f
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 0x5e782d178d…db5318
Audit this contract →
← previous block·next block →recent activity