← previous blocknext block →recent activity
Analyzing
Block #87,712,877
13 transactions · 12 stateful · 2026-07-14 13:55:17 UTC
Parallelism
77/100
Blocked
33%
Avg conflicts / tx
0.38
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #87,712,877 · 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
2w05w16w07w18w212w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x560ed681…07e6
0x34b655…2a6f
6 touches
3 conflicts
0xb95e925b…392d
0x34b655…2a6f
4 touches
1 conflict
0xbf78ee7f…e7fd
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0xa6afd3…d132
4 touches
1 conflict
0x1a287886…0266
0xa6afd3…d132
4 touches
1 conflict
0xfa551be3…a911
0xa6afd3…d132
4 touches
1 conflict
0x563ae507…382e
0x34b655…2a6f
2 touches
0 conflicts
0x5a7eb2ab…75a0
0x34b655…2a6f
2 touches
0 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
3 conflicts on slot 0x560ed68159…1e07e6
Audit this contract →
← previous block·next block →recent activity