← previous blocknext block →recent activity
Analyzing
Block #87,624,345
21 transactions · 20 stateful · 2026-07-14 04:03:16 UTC
Parallelism
52/100
Blocked
55%
Avg conflicts / tx
2
Longest chain
10 deep
Execution timeline
did this block parallelize well?
view
block #87,624,345 · 21 txs across 10 waves · depth 10
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w46w57w68w719w8
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x08330b36…ae29
0x34b655…2a6f
18 touches
36 conflicts
0x5b145de0…367c
0xc8689a…ee79
16 touches
28 conflicts
0x4560e5a8…b741
0x34b655…2a6f
16 touches
28 conflicts
0x49f75237…44f4
0x34b655…2a6f
16 touches
28 conflicts
0x6fe7d366…78ff
0x34b655…2a6f
16 touches
28 conflicts
0x7837c02d…0965
0x34b655…2a6f
16 touches
28 conflicts
0x91d48be7…e4e8
0x34b655…2a6f
16 touches
28 conflicts
0x9599eb41…b5d6
0x34b655…2a6f
16 touches
28 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
36 conflicts on slot 0x08330b3687…a7ae29
Audit this contract →
← previous block·next block →recent activity