← previous blocknext block →recent activity
Analyzing
Block #87,319,286
14 transactions · 13 stateful · 2026-07-12 18:02:20 UTC
Parallelism
79/100
Blocked
38%
Avg conflicts / tx
0.5
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #87,319,286 · 14 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w05w17w213w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x96047c45…b64a
0x34b655…2a6f
6 touches
3 conflicts
0xa4e5e0c2…6e04
0x34b655…2a6f
6 touches
3 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
6 touches
3 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
6 touches
3 conflicts
0xa2b9c6a5…6ab2
0x34b655…2a6f
4 touches
1 conflict
0x79d50d4a…951d
0x34b655…2a6f
4 touches
1 conflict
0x9e973d47…82e7
0x34b655…2a6f
4 touches
1 conflict
0x49ad3925…c3a4
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 0x96047c45d5…89b64a
Audit this contract →
← previous block·next block →recent activity