← previous blocknext block →recent activity
Analyzing
Block #87,592,828
10 transactions · 7 stateful · 2026-07-14 00:32:31 UTC
Parallelism
80/100
Blocked
14%
Avg conflicts / tx
0.1
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #87,592,828 · 10 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
4w06w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa3c36de0…3cf3
0x34b655…2a6f
4 touches
1 conflict
0xa9660e2b…64df
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4aa
0x34b655…2a6f
4 touches
1 conflict
0x92385428…6941
0x34b655…2a6f
4 touches
1 conflict
0x0f3050b5…c2d3
0x34b655…2a6f
2 touches
0 conflicts
0x6f4e7625…aba5
0x34b655…2a6f
2 touches
0 conflicts
0xc2b37cdc…e470
0x34b655…2a6f
2 touches
0 conflicts
0xf6deafb5…5c25
0x34b655…2a6f
2 touches
0 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
1 conflict on slot 0xa3c36de067…543cf3
Audit this contract →
← previous block·next block →recent activity