← previous blocknext block →recent activity
Analyzing
Block #87,705,023
29 transactions · 23 stateful · 2026-07-14 13:02:42 UTC
Parallelism
83/100
Blocked
39%
Avg conflicts / tx
0.59
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #87,705,023 · 29 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
1w05w18w09w112w013w114w218w019w020w222w123w226w327w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xab5ba139…ea6f
0x34b655…2a6f
8 touches
6 conflicts
0x6fe7d366…78ff
0x34b655…2a6f
6 touches
3 conflicts
0xc5031114…58ac
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…003d
0xa6afd3…d132
6 touches
3 conflicts
0x43ad566a…ebd8
0x34b655…2a6f
4 touches
1 conflict
0x6762cac2…3fb0
0x34b655…2a6f
4 touches
1 conflict
0x737aaf8a…5f24
0x34b655…2a6f
4 touches
1 conflict
0xa57576bb…e01f
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 0xab5ba139f3…9fea6f
Audit this contract →
← previous block·next block →recent activity