← previous blocknext block →recent activity
Analyzing
Block #87,624,461
25 transactions · 20 stateful · 2026-07-14 04:04:02 UTC
Parallelism
68/100
Blocked
45%
Avg conflicts / tx
1
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #87,624,461 · 25 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w46w57w48w515w623w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
10 touches
10 conflicts
0x42341814…60f1
0x34b655…2a6f
10 touches
10 conflicts
0x523e484a…6783
0x34b655…2a6f
8 touches
6 conflicts
0xd7fe05cd…207e
0x34b655…2a6f
8 touches
6 conflicts
0x08330b36…ae29
0x34b655…2a6f
8 touches
6 conflicts
0x68b75835…d6f3
0x34b655…2a6f
6 touches
3 conflicts
0x7dd7c981…106b
0x34b655…2a6f
6 touches
3 conflicts
0x88cbd993…f3c9
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