← previous blocknext block →recent activity
Analyzing
Block #85,573,380
22 transactions · 14 stateful · 2026-07-04 15:41:01 UTC
Parallelism
91/100
Blocked
14%
Avg conflicts / tx
0.09
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #85,573,380 · 22 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
2w05w19w020w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x517d35c7…f359
0x34b655…2a6f
4 touches
1 conflict
0x0d622e34…0000
0x681e90…ae09
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
2 touches
0 conflicts
0x1df9a53f…21bc
0x065c9d…c394
2 touches
0 conflicts
0x33589eda…c5ac
0x065c9d…c394
2 touches
0 conflicts
0x699cbd38…f50a
0x065c9d…c394
2 touches
0 conflicts
0x6ce33c70…9115
0x065c9d…c394
2 touches
0 conflicts
0x706de706…00ee
0x065c9d…c394
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 0x517d35c7d4…69f359
Audit this contract →
← previous block·next block →recent activity