← previous blocknext block →recent activity
Analyzing
Block #87,624,087
26 transactions · 22 stateful · 2026-07-14 04:01:32 UTC
Parallelism
77/100
Blocked
45%
Avg conflicts / tx
0.81
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #87,624,087 · 26 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
1w04w07w19w210w311w414w215w316w418w119w020w522w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
8 touches
6 conflicts
0xf2f4727d…cdb7
0x34b655…2a6f
8 touches
6 conflicts
0x02679875…8d2f
0x34b655…2a6f
8 touches
6 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
6 touches
3 conflicts
0x8262a588…40bd
0x34b655…2a6f
6 touches
3 conflicts
0x9599eb41…b5d6
0x34b655…2a6f
6 touches
3 conflicts
0xa24365bc…5064
0x34b655…2a6f
6 touches
3 conflicts
0xcd206b7a…abf6
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
6 conflicts on slot 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity