← previous blocknext block →recent activity
Analyzing
Block #87,354,898
23 transactions · 23 stateful · 2026-07-12 22:00:29 UTC
Parallelism
78/100
Blocked
39%
Avg conflicts / tx
0.7
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #87,354,898 · 23 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
1w02w13w04w15w26w37w412w013w114w216w217w018w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfaef08b1…0696
0x34b655…2a6f
10 touches
10 conflicts
0x8a35acfb…d1ac
0xb1dbf0…c0d3
5 touches
3 conflicts
0x0a5529a7…492e
0x34b655…2a6f
4 touches
1 conflict
0x1299b030…e115
0x34b655…2a6f
4 touches
1 conflict
0x1aef6331…1390
0x34b655…2a6f
4 touches
1 conflict
0x211317f0…380b
0x34b655…2a6f
4 touches
1 conflict
0x2328941c…84d3
0x34b655…2a6f
4 touches
1 conflict
0x24b6091e…d294
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 0xfaef08b108…f90696
Audit this contract →
← previous block·next block →recent activity