← previous blocknext block →recent activity
Analyzing
Block #87,624,928
16 transactions · 14 stateful · 2026-07-14 04:07:10 UTC
Parallelism
63/100
Blocked
57%
Avg conflicts / tx
1.38
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #87,624,928 · 16 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
1w02w13w24w36w07w19w210w311w415w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x08330b36…ae29
0x34b655…2a6f
12 touches
15 conflicts
0x5e0b8bbe…377b
0x34b655…2a6f
10 touches
10 conflicts
0x6fe7d366…78ff
0x34b655…2a6f
10 touches
10 conflicts
0x9599eb41…b5d6
0x34b655…2a6f
10 touches
10 conflicts
0xbabe821d…939b
0x34b655…2a6f
10 touches
10 conflicts
0x91d48be7…e4e8
0x34b655…2a6f
9 touches
10 conflicts
0x13510de3…1c68
0x34b655…2a6f
9 touches
10 conflicts
0x5b145de0…367c
0xc8689a…ee79
8 touches
6 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
15 conflicts on slot 0x08330b3687…a7ae29
Audit this contract →
← previous block·next block →recent activity