← previous blocknext block →recent activity
Analyzing
Block #87,302,237
16 transactions · 15 stateful · 2026-07-12 16:08:21 UTC
Parallelism
81/100
Blocked
27%
Avg conflicts / tx
0.31
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #87,302,237 · 16 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
2w06w07w110w111w215w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xdfd64ea5…015c
0x34b655…2a6f
4 touches
1 conflict
0xe85e763f…3b25
0x34b655…2a6f
4 touches
1 conflict
0x013c31f5…a717
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0xa6afd3…d132
4 touches
1 conflict
0x013c31f5…a718
0x34b655…2a6f
4 touches
1 conflict
0x373f6c27…fd7a
0x34b655…2a6f
4 touches
1 conflict
0x5a13f403…8d04
0x34b655…2a6f
4 touches
1 conflict
0x64aaadbf…f9f3
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
1 conflict on slot 0xdfd64ea578…1e015c
Audit this contract →
← previous block·next block →recent activity