← previous blocknext block →recent activity
Analyzing
Block #87,578,830
13 transactions · 9 stateful · 2026-07-13 22:58:54 UTC
Parallelism
77/100
Blocked
44%
Avg conflicts / tx
0.46
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #87,578,830 · 13 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
1w02w13w04w16w17w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x2b5101ac…090b
0x34b655…2a6f
6 touches
3 conflicts
0x1b39afc7…4e44
0x34b655…2a6f
4 touches
1 conflict
0x1b5f5a50…c006
0x34b655…2a6f
4 touches
1 conflict
0x20134ee4…87a3
0x34b655…2a6f
4 touches
1 conflict
0x2a88784d…f1be
0x34b655…2a6f
4 touches
1 conflict
0x375c6d28…d03d
0x34b655…2a6f
4 touches
1 conflict
0x3b4e6b38…bd6a
0x34b655…2a6f
4 touches
1 conflict
0x4f1e16d4…4833
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 0x2b5101acd1…7c090b
Audit this contract →
← previous block·next block →recent activity