← previous blocknext block →recent activity
Analyzing
Block #86,507,015
24 transactions · 19 stateful · 2026-07-08 23:30:32 UTC
Parallelism
67/100
Blocked
42%
Avg conflicts / tx
1.08
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #86,507,015 · 24 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
3w05w09w115w116w217w318w420w522w623w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
14 touches
21 conflicts
0x64aaadbf…f9f3
0x34b655…2a6f
10 touches
10 conflicts
0x37ee30c9…9e70
0x34b655…2a6f
6 touches
3 conflicts
0x258fcaf5…2084
0x34b655…2a6f
4 touches
1 conflict
0x2d94ecd9…43db
0x34b655…2a6f
4 touches
1 conflict
0x469dac8d…3411
0x34b655…2a6f
4 touches
1 conflict
0x64a785e4…0110
0x34b655…2a6f
4 touches
1 conflict
0x7a8cad7f…48cd
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
21 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity