← previous blocknext block →recent activity
Analyzing
Block #86,835,200
28 transactions · 25 stateful · 2026-07-10 12:06:09 UTC
Parallelism
71/100
Blocked
52%
Avg conflicts / tx
1.46
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #86,835,200 · 28 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
4w05w16w27w38w49w510w611w719w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x03fb27fd…0c06
0x34b655…2a6f
16 touches
28 conflicts
0x3483ab79…8ed3
0x34b655…2a6f
16 touches
28 conflicts
0x63c900f4…2600
0x34b655…2a6f
16 touches
28 conflicts
0x7523ad90…2ba5
0x34b655…2a6f
16 touches
28 conflicts
0x9f40a209…1193
0x34b655…2a6f
16 touches
28 conflicts
0xc0b9bd73…7f1c
0x34b655…2a6f
16 touches
28 conflicts
0xfaef08b1…0696
0x34b655…2a6f
16 touches
28 conflicts
0x922c7ebd…6600
0xc8689a…ee79
16 touches
28 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
28 conflicts on slot 0x03fb27fddd…f00c06
Audit this contract →
← previous block·next block →recent activity