← previous blocknext block →recent activity
Analyzing
Block #86,881,496
18 transactions · 17 stateful · 2026-07-10 17:15:45 UTC
Parallelism
72/100
Blocked
29%
Avg conflicts / tx
0.67
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #86,881,496 · 18 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
4w05w16w27w38w417w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd58b9a66…1c23
0x34b655…2a6f
10 touches
10 conflicts
0x922c7ebd…6600
0xc8689a…ee79
10 touches
10 conflicts
0xfaef08b1…0696
0x34b655…2a6f
10 touches
10 conflicts
0x288bc578…318e
0x34b655…2a6f
10 touches
10 conflicts
0x39c051d9…0418
0x34b655…2a6f
10 touches
10 conflicts
0x4327afd2…1b3a
0x34b655…2a6f
10 touches
10 conflicts
0x5e02109f…c11b
0x34b655…2a6f
10 touches
10 conflicts
0x3133f94b…f76b
0x34b655…2a6f
9 touches
10 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
10 conflicts on slot 0xd58b9a66f8…5f1c23
Audit this contract →
← previous block·next block →recent activity