← previous blocknext block →recent activity
Analyzing
Block #87,621,796
23 transactions · 21 stateful · 2026-07-14 03:46:13 UTC
Parallelism
83/100
Blocked
38%
Avg conflicts / tx
0.65
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #87,621,796 · 23 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
1w05w06w110w011w112w213w114w116w020w121w122w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x640530ff…86bc
0x34b655…2a6f
8 touches
6 conflicts
0x745952b2…d90c
0x34b655…2a6f
6 touches
3 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
6 touches
3 conflicts
0x1737ef68…1e55
0x34b655…2a6f
4 touches
1 conflict
0x20067ecb…0e41
0x34b655…2a6f
4 touches
1 conflict
0x6ba89834…1826
0x34b655…2a6f
4 touches
1 conflict
0x6fe7d366…78ff
0x34b655…2a6f
4 touches
1 conflict
0x7c7eff13…16db
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
6 conflicts on slot 0x640530ff6c…0186bc
Audit this contract →
← previous block·next block →recent activity