← previous blocknext block →recent activity
Analyzing
Block #87,592,398
24 transactions · 22 stateful · 2026-07-14 00:29:38 UTC
Parallelism
75/100
Blocked
45%
Avg conflicts / tx
0.88
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #87,592,398 · 24 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
1w03w15w06w17w08w19w210w311w012w316w417w220w021w123w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x69ce640b…884a
0x34b655…2a6f
10 touches
10 conflicts
0x6fe7d366…78ff
0x34b655…2a6f
8 touches
6 conflicts
0x0eeb2a30…6909
0x34b655…2a6f
6 touches
3 conflicts
0xac089f8b…0a04
0x34b655…2a6f
6 touches
3 conflicts
0x74a7b40b…8922
0x34b655…2a6f
4 touches
1 conflict
0x8250b8db…a970
0x34b655…2a6f
4 touches
1 conflict
0x84c10eee…c90e
0x34b655…2a6f
4 touches
1 conflict
0x94b8fa5e…924f
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
10 conflicts on slot 0x69ce640b96…ed884a
Audit this contract →
← previous block·next block →recent activity