← previous blocknext block →recent activity
Analyzing
Block #87,325,858
19 transactions · 19 stateful · 2026-07-12 18:46:20 UTC
Parallelism
79/100
Blocked
32%
Avg conflicts / tx
0.53
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #87,325,858 · 19 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w06w010w111w112w213w014w115w216w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x8b2a0716…52ab
0x0a2fbf…29b1
8 touches
6 conflicts
0x8b2a0716…52ae
0x0a2fbf…29b1
8 touches
6 conflicts
0xfed9f9c5…5b15
0x0a2fbf…29b1
8 touches
6 conflicts
0x00000000…0005
0x370e2e…63b4
8 touches
6 conflicts
0x00000000…0006
0x0a2fbf…29b1
8 touches
6 conflicts
0x8b2a0716…52aa
0x0a2fbf…29b1
8 touches
6 conflicts
0x55b4e430…44cb
0x754704…b603
8 touches
6 conflicts
0xfed9f9c5…5b16
0x0a2fbf…29b1
8 touches
6 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: 0x0a2fbf2d…f729b1
6 conflicts on slot 0x8b2a071659…9852ab
Audit this contract →
← previous block·next block →recent activity