← previous blocknext block →recent activity
Analyzing
Block #87,628,668
15 transactions · 11 stateful · 2026-07-14 04:32:13 UTC
Parallelism
73/100
Blocked
36%
Avg conflicts / tx
0.4
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #87,628,668 · 15 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
1w02w15w06w17w29w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7e5ea60a…c4aa
0x34b655…2a6f
6 touches
3 conflicts
0x92385428…6941
0x34b655…2a6f
6 touches
3 conflicts
0xcc13c07b…d7cc
0x34b655…2a6f
4 touches
1 conflict
0x82e3f65a…d23c
0x34b655…2a6f
4 touches
1 conflict
0x8cca2254…7982
0x34b655…2a6f
4 touches
1 conflict
0x97884f85…7818
0x34b655…2a6f
4 touches
1 conflict
0xa97ad8e6…fb2d
0x34b655…2a6f
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 0x7e5ea60ab2…b0c4aa
Audit this contract →
← previous block·next block →recent activity