← previous blocknext block →recent activity
Analyzing
Block #87,317,592
11 transactions · 11 stateful · 2026-07-12 17:51:02 UTC
Parallelism
64/100
Blocked
27%
Avg conflicts / tx
0.55
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #87,317,592 · 11 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
5w06w17w28w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0733be30…112f
0x34b655…2a6f
8 touches
6 conflicts
0x64aaadbf…f9f3
0x34b655…2a6f
6 touches
3 conflicts
0x37ee30c9…9e70
0x34b655…2a6f
6 touches
3 conflicts
0x14365e4a…779e
0x34b655…2a6f
4 touches
1 conflict
0x36a85feb…891b
0x34b655…2a6f
4 touches
1 conflict
0xccdc32f8…72be
0x34b655…2a6f
4 touches
1 conflict
0x42523a73…c021
0x34b655…2a6f
4 touches
1 conflict
0x58f65aa1…8f98
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 0x0733be30d6…38112f
Audit this contract →
← previous block·next block →recent activity