← previous blocknext block →recent activity
Analyzing
Block #87,703,653
25 transactions · 22 stateful · 2026-07-14 12:53:31 UTC
Parallelism
76/100
Blocked
41%
Avg conflicts / tx
0.6
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #87,703,653 · 25 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
1w03w04w15w06w17w28w39w010w111w212w413w520w021w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…003d
0xa6afd3…d132
6 touches
3 conflicts
0xacdf56b3…e33c
0xa6afd3…d132
6 touches
3 conflicts
0xee3b1b53…77dd
0xa6afd3…d132
6 touches
3 conflicts
0xdfc21d7c…e062
0x34b655…2a6f
6 touches
3 conflicts
0x662691d9…623c
0x34b655…2a6f
4 touches
1 conflict
0x67905f6e…02a1
0x34b655…2a6f
4 touches
1 conflict
0x92385428…6941
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