← previous blocknext block →recent activity
Analyzing
Block #87,307,740
14 transactions · 13 stateful · 2026-07-12 16:45:08 UTC
Parallelism
64/100
Blocked
38%
Avg conflicts / tx
0.57
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #87,307,740 · 14 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
1w04w15w27w38w411w013w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0733be30…112f
0x34b655…2a6f
8 touches
6 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xdfaac0ae…d0e1
0x34b655…2a6f
4 touches
1 conflict
0x95c9704c…8a57
0x34b655…2a6f
4 touches
1 conflict
0xb8fa82de…4414
0x34b655…2a6f
4 touches
1 conflict
0xbdf1e736…db04
0x34b655…2a6f
4 touches
1 conflict
0xc5f336ca…912e
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 0x0733be30d6…38112f
Audit this contract →
← previous block·next block →recent activity