← previous blocknext block →recent activity
Analyzing
Block #87,518,344
26 transactions · 22 stateful · 2026-07-13 16:13:46 UTC
Parallelism
81/100
Blocked
41%
Avg conflicts / tx
0.46
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #87,518,344 · 26 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
1w02w13w14w25w011w112w213w316w320w424w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
6 touches
3 conflicts
0x889d5e90…929a
0x2a68ba…90c5
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xb9266685…8b1d
0x34b655…2a6f
4 touches
1 conflict
0xb284eda2…a999
0x34b655…2a6f
4 touches
1 conflict
0xafb2524a…0ce4
0x34b655…2a6f
4 touches
1 conflict
0x419cbce1…3d2d
0x34b655…2a6f
4 touches
1 conflict
0x69ce640b…884a
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
3 conflicts on slot 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity