← previous blocknext block →recent activity
Analyzing
Block #87,596,962
18 transactions · 16 stateful · 2026-07-14 01:00:11 UTC
Parallelism
72/100
Blocked
50%
Avg conflicts / tx
0.89
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #87,596,962 · 18 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w04w17w210w011w112w313w414w216w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x05ae4d3e…3c79
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0xf3d10975…0d07
0x34b655…2a6f
6 touches
3 conflicts
0x7ff47f28…41a8
0x34b655…2a6f
6 touches
3 conflicts
0xa1210206…7aff
0x34b655…2a6f
6 touches
3 conflicts
0xea02471d…1542
0x34b655…2a6f
6 touches
3 conflicts
0xf31b6b3f…055e
0x34b655…2a6f
6 touches
3 conflicts
0x198a44fd…98d2
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 0x05ae4d3e77…953c79
Audit this contract →
← previous block·next block →recent activity