← previous blocknext block →recent activity
Analyzing
Block #87,710,875
13 transactions · 11 stateful · 2026-07-14 13:41:53 UTC
Parallelism
85/100
Blocked
9%
Avg conflicts / tx
0.08
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #87,710,875 · 13 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w06w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x3c1aac7c…b2f4
0x34b655…2a6f
4 touches
1 conflict
0xea02471d…1542
0x34b655…2a6f
4 touches
1 conflict
0x3817764d…242b
0x34b655…2a6f
2 touches
0 conflicts
0x3e950538…2259
0x34b655…2a6f
2 touches
0 conflicts
0x3eeca510…5146
0x34b655…2a6f
2 touches
0 conflicts
0x4f1e16d4…4833
0x34b655…2a6f
2 touches
0 conflicts
0x6e857271…94b0
0x34b655…2a6f
2 touches
0 conflicts
0x6fe7d366…78ff
0x34b655…2a6f
2 touches
0 conflicts
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 0x3c1aac7cc0…f7b2f4
Audit this contract →
← previous block·next block →recent activity