← previous blocknext block →recent activity
Analyzing
Block #86,623,869
23 transactions · 20 stateful · 2026-07-09 12:33:09 UTC
Parallelism
70/100
Blocked
35%
Avg conflicts / tx
0.7
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #86,623,869 · 23 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
3w04w16w29w317w018w319w420w521w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
10 touches
10 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
6 touches
3 conflicts
0x70b87e4d…65d5
0x34b655…2a6f
6 touches
3 conflicts
0xfbd04d13…95f3
0x34b655…2a6f
4 touches
1 conflict
0xe01fb5e1…e8e8
0x34b655…2a6f
4 touches
1 conflict
0xe5816326…db11
0x34b655…2a6f
4 touches
1 conflict
0xeaa801fb…dda1
0x34b655…2a6f
4 touches
1 conflict
0xfaef08b1…0696
0x34b655…2a6f
4 touches
1 conflict
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
10 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity