← previous blocknext block →recent activity
Analyzing
Block #87,624,993
21 transactions · 19 stateful · 2026-07-14 04:07:36 UTC
Parallelism
81/100
Blocked
47%
Avg conflicts / tx
0.9
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #87,624,993 · 21 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w05w16w27w09w310w011w114w117w320w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd7fe05cd…207e
0x34b655…2a6f
8 touches
6 conflicts
0x1ee4a6d2…6389
0x34b655…2a6f
8 touches
6 conflicts
0x42341814…60f1
0x34b655…2a6f
8 touches
6 conflicts
0x756ad195…36a3
0x34b655…2a6f
8 touches
6 conflicts
0x17c70f19…23a7
0x34b655…2a6f
6 touches
3 conflicts
0x8093d3a9…89b1
0x34b655…2a6f
6 touches
3 conflicts
0x21158693…63e2
0x34b655…2a6f
6 touches
3 conflicts
0x366c7d57…0ed1
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
6 conflicts on slot 0xd7fe05cdfa…d0207e
Audit this contract →
← previous block·next block →recent activity