← previous blocknext block →recent activity
Analyzing
Block #86,798,425
19 transactions · 15 stateful · 2026-07-10 08:00:08 UTC
Parallelism
63/100
Blocked
47%
Avg conflicts / tx
0.58
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #86,798,425 · 19 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w04w05w16w27w38w49w512w113w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0733be30…112f
0x34b655…2a6f
8 touches
6 conflicts
0xaedc3dd6…3c3b
0x34b655…2a6f
6 touches
3 conflicts
0x0b9f02c4…6fec
0x34b655…2a6f
6 touches
3 conflicts
0xb8ca5cb8…ceaa
0x34b655…2a6f
6 touches
3 conflicts
0x1191dbf7…8e85
0x34b655…2a6f
6 touches
3 conflicts
0xdd81afb3…de3d
0x34b655…2a6f
6 touches
3 conflicts
0xf5eb217d…27b5
0x34b655…2a6f
6 touches
3 conflicts
0xfaef08b1…0696
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 0x0733be30d6…38112f
Audit this contract →
← previous block·next block →recent activity