← previous blocknext block →recent activity
Analyzing
Block #87,581,098
21 transactions · 17 stateful · 2026-07-13 23:14:04 UTC
Parallelism
81/100
Blocked
35%
Avg conflicts / tx
0.48
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #87,581,098 · 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
1w02w14w05w17w010w011w112w214w319w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x040d237c…b53c
0x34b655…2a6f
6 touches
3 conflicts
0x7527802e…2ba9
0x34b655…2a6f
6 touches
3 conflicts
0x8bf661cb…bcd2
0x34b655…2a6f
6 touches
3 conflicts
0x17c70f19…23a7
0x34b655…2a6f
4 touches
1 conflict
0x18904470…0ef9
0x34b655…2a6f
4 touches
1 conflict
0x1d099f02…4793
0x34b655…2a6f
4 touches
1 conflict
0x20a110e8…918d
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
3 conflicts on slot 0x040d237c10…e0b53c
Audit this contract →
← previous block·next block →recent activity