← previous blocknext block →recent activity
Analyzing
Block #87,351,389
14 transactions · 13 stateful · 2026-07-12 21:37:01 UTC
Parallelism
71/100
Blocked
31%
Avg conflicts / tx
0.57
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #87,351,389 · 14 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w05w06w17w08w29w110w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x08547d8c…14ff
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…003d
0xa6afd3…d132
4 touches
1 conflict
0xc8f6f7a3…f564
0x34b655…2a6f
4 touches
1 conflict
0xd6c45a31…9931
0x34b655…2a6f
4 touches
1 conflict
0xdad3be8c…a703
0x34b655…2a6f
4 touches
1 conflict
0xdb89ef9a…606c
0x34b655…2a6f
4 touches
1 conflict
0xefd93ead…49ac
0x34b655…2a6f
4 touches
1 conflict
0x0733be30…112f
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 0x08547d8c30…3d14ff
Audit this contract →
← previous block·next block →recent activity