← previous blocknext block →recent activity
Analyzing
Block #87,612,697
14 transactions · 12 stateful · 2026-07-14 02:45:23 UTC
Parallelism
71/100
Blocked
33%
Avg conflicts / tx
0.43
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #87,612,697 · 14 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
1w02w13w04w25w38w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x1f6f8ff8…a5d4
0x34b655…2a6f
6 touches
3 conflicts
0x2bfb71b5…3a04
0x34b655…2a6f
6 touches
3 conflicts
0x92385428…6941
0x34b655…2a6f
6 touches
3 conflicts
0xdf06241e…adf9
0x34b655…2a6f
6 touches
3 conflicts
0x04095623…2e2a
0x34b655…2a6f
6 touches
3 conflicts
0x4b0a67ef…b8ba
0x34b655…2a6f
4 touches
1 conflict
0x4f7a2ec0…9ace
0x34b655…2a6f
4 touches
1 conflict
0x6fe7d366…78ff
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 0x1f6f8ff893…67a5d4
Audit this contract →
← previous block·next block →recent activity