← previous blocknext block →recent activity
Analyzing
Block #87,594,044
22 transactions · 21 stateful · 2026-07-14 00:40:39 UTC
Parallelism
73/100
Blocked
33%
Avg conflicts / tx
0.59
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #87,594,044 · 22 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
2w04w17w28w39w411w012w013w414w515w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
8 touches
6 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
6 touches
3 conflicts
0x2df6f59b…d662
0x34b655…2a6f
4 touches
1 conflict
0x34255408…cdd1
0x34b655…2a6f
4 touches
1 conflict
0x41b6b63a…6739
0x34b655…2a6f
4 touches
1 conflict
0x46fdb575…fe2d
0x34b655…2a6f
4 touches
1 conflict
0x63f8a50d…333b
0x34b655…2a6f
4 touches
1 conflict
0x64e9ea4a…ca6c
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
6 conflicts on slot 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity