← previous blocknext block →recent activity
Analyzing
Block #85,352,448
13 transactions · 9 stateful · 2026-07-03 15:09:56 UTC
Parallelism
85/100
Blocked
11%
Avg conflicts / tx
0.08
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #85,352,448 · 13 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
1w012w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x67905f6e…02a1
0x34b655…2a6f
4 touches
1 conflict
0x08d66073…e706
0x34b655…2a6f
4 touches
1 conflict
0xae897e60…a112
0x34b655…2a6f
4 touches
1 conflict
0x05d6ac06…2ebe
0x34b655…2a6f
2 touches
0 conflicts
0x077d58c3…8ed7
0x34b655…2a6f
2 touches
0 conflicts
0x16a84933…93de
0x34b655…2a6f
2 touches
0 conflicts
0x28358a8e…323d
0x34b655…2a6f
2 touches
0 conflicts
0x2ed98d3b…78ef
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 0x67905f6e13…0502a1
Audit this contract →
← previous block·next block →recent activity