← previous blocknext block →recent activity
Analyzing
Block #87,577,668
15 transactions · 14 stateful · 2026-07-13 22:51:07 UTC
Parallelism
73/100
Blocked
43%
Avg conflicts / tx
0.6
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #87,577,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
1w02w03w14w05w18w09w110w211w112w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x1e6e9104…f143
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…0002
0x04fdea…47d7
4 touches
1 conflict
0x0733be30…112f
0x34b655…2a6f
4 touches
1 conflict
0x109e6370…4cb8
0x34b655…2a6f
4 touches
1 conflict
0x109e6370…4cb9
0x34b655…2a6f
4 touches
1 conflict
0x00000000…0001
0xc1ff9f…b0fc
4 touches
1 conflict
0xc2f84a16…86b8
0x34b655…2a6f
4 touches
1 conflict
0xef856bd6…36ea
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
3 conflicts on slot 0x1e6e9104e8…06f143
Audit this contract →
← previous block·next block →recent activity