← previous blocknext block →recent activity
Analyzing
Block #87,315,357
18 transactions · 16 stateful · 2026-07-12 17:36:04 UTC
Parallelism
67/100
Blocked
50%
Avg conflicts / tx
1.33
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #87,315,357 · 18 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
2w03w14w05w26w37w410w011w112w213w317w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x924bac95…3f39
0x34b655…2a6f
10 touches
10 conflicts
0x71641e8d…a781
0x34b655…2a6f
10 touches
10 conflicts
0xdc0f0c56…351c
0x34b655…2a6f
8 touches
6 conflicts
0xfaef08b1…0696
0x34b655…2a6f
8 touches
6 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0x548145a9…cfce
0x34b655…2a6f
6 touches
3 conflicts
0x63b15849…80b2
0x34b655…2a6f
6 touches
3 conflicts
0x63c900f4…2600
0x34b655…2a6f
6 touches
3 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 0x924bac955e…793f39
Audit this contract →
← previous block·next block →recent activity