← previous blocknext block →recent activity
Analyzing
Block #87,302,724
14 transactions · 12 stateful · 2026-07-12 16:11:36 UTC
Parallelism
79/100
Blocked
25%
Avg conflicts / tx
0.29
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #87,302,724 · 14 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w04w05w18w112w013w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0733be30…112f
0x34b655…2a6f
4 touches
1 conflict
0x135cdc1d…7b2f
0x34b655…2a6f
4 touches
1 conflict
0x2f4b1dc8…e9fa
0x34b655…2a6f
4 touches
1 conflict
0x4b482505…30c1
0x34b655…2a6f
4 touches
1 conflict
0x534750fd…f701
0x34b655…2a6f
4 touches
1 conflict
0x5e782d17…5317
0x34b655…2a6f
4 touches
1 conflict
0x5e782d17…5318
0x34b655…2a6f
4 touches
1 conflict
0x5ee561f5…1e7f
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
1 conflict on slot 0x0733be30d6…38112f
Audit this contract →
← previous block·next block →recent activity