← previous blocknext block →recent activity
Analyzing
Block #87,408,072
19 transactions · 18 stateful · 2026-07-13 03:56:09 UTC
Parallelism
79/100
Blocked
39%
Avg conflicts / tx
0.79
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #87,408,072 · 19 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
4w05w16w07w18w210w112w213w317w018w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x2b5101ac…090b
0x34b655…2a6f
8 touches
6 conflicts
0x0733be30…112f
0x34b655…2a6f
6 touches
3 conflicts
0x9b36f19f…fa5a
0x34b655…2a6f
6 touches
3 conflicts
0xc80d6588…46bc
0x34b655…2a6f
6 touches
3 conflicts
0xcfddc3ab…e671
0x34b655…2a6f
6 touches
3 conflicts
0xe181f491…f4e3
0x34b655…2a6f
6 touches
3 conflicts
0xfe3d37ee…6e67
0x34b655…2a6f
6 touches
3 conflicts
0x8a35acfb…d1ad
0xb1dbf0…c0d3
6 touches
3 conflicts
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 0x2b5101acd1…7c090b
Audit this contract →
← previous block·next block →recent activity