← previous blocknext block →recent activity
Analyzing
Block #87,877,245
39 transactions · 24 stateful · 2026-07-15 08:14:53 UTC
Parallelism
92/100
Blocked
38%
Avg conflicts / tx
0.31
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #87,877,245 · 39 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
1w010w111w014w115w116w222w023w125w026w131w232w033w136w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x974c36fe…1cd7
0x34b655…2a6f
6 touches
3 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
6 touches
3 conflicts
0x89899075…a940
0xd32edf…ff58
5 touches
3 conflicts
0x44ad89ba…cf83
0x0cc9b2…7777
4 touches
1 conflict
0x99a3a7c1…1e2b
0x0cc9b2…7777
4 touches
1 conflict
0x01e7b865…6e6d
0x188d58…ea8e
4 touches
1 conflict
0x01e7b865…6e6e
0x188d58…ea8e
4 touches
1 conflict
0x889d5e90…929a
0x2a68ba…90c5
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
3 conflicts on slot 0x974c36fe03…4f1cd7
Audit this contract →
← previous block·next block →recent activity