← previous blocknext block →recent activity
Analyzing
Block #87,624,661
14 transactions · 13 stateful · 2026-07-14 04:05:23 UTC
Parallelism
57/100
Blocked
54%
Avg conflicts / tx
1.07
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #87,624,661 · 14 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w49w110w213w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
10 touches
10 conflicts
0x08330b36…ae29
0x34b655…2a6f
8 touches
6 conflicts
0x1b86c265…03e2
0x34b655…2a6f
6 touches
3 conflicts
0xbabe821d…939b
0x34b655…2a6f
6 touches
3 conflicts
0x49f75237…44f4
0x34b655…2a6f
6 touches
3 conflicts
0xd19c9d38…b459
0x34b655…2a6f
6 touches
3 conflicts
0xed59b1cd…8509
0x34b655…2a6f
6 touches
3 conflicts
0x5e0b8bbe…377b
0x34b655…2a6f
6 touches
3 conflicts
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 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity