← previous blocknext block →recent activity
Analyzing
Block #86,802,946
25 transactions · 22 stateful · 2026-07-10 08:30:22 UTC
Parallelism
72/100
Blocked
55%
Avg conflicts / tx
1.2
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #86,802,946 · 25 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
2w04w05w16w27w38w49w510w011w116w017w218w119w120w223w524w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfaef08b1…0696
0x34b655…2a6f
12 touches
15 conflicts
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0xd99b3b64…1c95
0x34b655…2a6f
6 touches
3 conflicts
0x0a886dc3…5876
0x34b655…2a6f
4 touches
1 conflict
0x0afc2b4b…6890
0x34b655…2a6f
4 touches
1 conflict
0x0f4cddfd…3085
0x34b655…2a6f
4 touches
1 conflict
0x11d629eb…bcd9
0x34b655…2a6f
4 touches
1 conflict
0x22e0cc1d…ad0d
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
15 conflicts on slot 0xfaef08b108…f90696
Audit this contract →
← previous block·next block →recent activity