← previous blocknext block →recent activity
Analyzing
Block #87,594,302
29 transactions · 25 stateful · 2026-07-14 00:42:23 UTC
Parallelism
83/100
Blocked
52%
Avg conflicts / tx
0.83
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #87,594,302 · 29 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
1w03w16w07w18w29w310w011w112w214w315w218w319w321w227w328w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x2b5101ac…090b
0x34b655…2a6f
10 touches
10 conflicts
0x5f57e7ab…9f8d
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…0001
0xc1ff9f…b0fc
8 touches
6 conflicts
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0x160f117d…8e90
0x065c9d…c394
6 touches
3 conflicts
0x98aedeb3…243a
0x34b655…2a6f
6 touches
3 conflicts
0xc80d6588…46bc
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…002a
0x1b6862…e19c
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
10 conflicts on slot 0x2b5101acd1…7c090b
Audit this contract →
← previous block·next block →recent activity