← previous blocknext block →recent activity
Analyzing
Block #87,718,175
25 transactions · 24 stateful · 2026-07-14 14:30:53 UTC
Parallelism
84/100
Blocked
38%
Avg conflicts / tx
0.68
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #87,718,175 · 25 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
1w02w03w14w25w06w18w19w010w112w014w217w018w119w221w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5f234b05…db39
0x34b655…2a6f
8 touches
6 conflicts
0x5b33f5b9…4bab
0x34b655…2a6f
6 touches
3 conflicts
0x5bf44783…6166
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…000a
0x90c374…be45
6 touches
3 conflicts
0x00000000…000b
0x90c374…be45
6 touches
3 conflicts
0x1f2cd70b…94be
0x34b655…2a6f
4 touches
1 conflict
0x1f9b0e7a…59f1
0x34b655…2a6f
4 touches
1 conflict
0x2beb0ffe…28e0
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 0x5f234b05a2…82db39
Audit this contract →
← previous block·next block →recent activity