← previous blocknext block →recent activity
Analyzing
Block #87,624,881
15 transactions · 13 stateful · 2026-07-14 04:06:51 UTC
Parallelism
67/100
Blocked
38%
Avg conflicts / tx
0.8
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #87,624,881 · 15 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w38w010w113w014w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x1ee4a6d2…6389
0x34b655…2a6f
10 touches
10 conflicts
0x42341814…60f1
0x34b655…2a6f
8 touches
6 conflicts
0x0a6c9360…fbbb
0x34b655…2a6f
4 touches
1 conflict
0x0cc003e9…fefc
0x34b655…2a6f
4 touches
1 conflict
0x0dcb313d…7073
0x34b655…2a6f
4 touches
1 conflict
0x144c19ec…a635
0x34b655…2a6f
4 touches
1 conflict
0x17c70f19…23a7
0x34b655…2a6f
4 touches
1 conflict
0x21158693…63e2
0x34b655…2a6f
4 touches
1 conflict
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 0x1ee4a6d212…536389
Audit this contract →
← previous block·next block →recent activity