← previous blocknext block →recent activity
Analyzing
Block #86,447,329
24 transactions · 18 stateful · 2026-07-08 16:51:34 UTC
Parallelism
75/100
Blocked
39%
Avg conflicts / tx
0.5
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #86,447,329 · 24 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w06w07w110w112w215w116w021w322w423w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb624d2ea…8c87
0x34b655…2a6f
8 touches
6 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x9fb55ee7…8ecc
0xa6afd3…d132
4 touches
1 conflict
0x1630ed91…9774
0x34b655…2a6f
4 touches
1 conflict
0x2bf5914f…c75d
0x34b655…2a6f
4 touches
1 conflict
0x7dabce11…b51a
0x34b655…2a6f
4 touches
1 conflict
0xc8c615d4…5da3
0x34b655…2a6f
4 touches
1 conflict
0xd0f6f4f2…dffa
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
6 conflicts on slot 0xb624d2eae3…2b8c87
Audit this contract →
← previous block·next block →recent activity