← previous blocknext block →recent activity
Analyzing
Block #87,296,928
15 transactions · 13 stateful · 2026-07-12 15:32:53 UTC
Parallelism
67/100
Blocked
46%
Avg conflicts / tx
0.73
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #87,296,928 · 15 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
2w03w15w17w29w313w214w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbc94dfe1…0b3d
0x34b655…2a6f
8 touches
6 conflicts
0x64aaadbf…f9f3
0x34b655…2a6f
6 touches
3 conflicts
0xdb564c7f…72f9
0x34b655…2a6f
6 touches
3 conflicts
0x3586df10…f917
0x34b655…2a6f
4 touches
1 conflict
0x3be33cca…0fff
0x34b655…2a6f
4 touches
1 conflict
0x4da61c94…532a
0x34b655…2a6f
4 touches
1 conflict
0x737acb78…fce8
0x34b655…2a6f
4 touches
1 conflict
0x7634a3f4…7f24
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 0xbc94dfe1d8…a70b3d
Audit this contract →
← previous block·next block →recent activity