← previous blocknext block →recent activity
Analyzing
Block #87,585,350
13 transactions · 10 stateful · 2026-07-13 23:42:30 UTC
Parallelism
69/100
Blocked
30%
Avg conflicts / tx
0.38
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #87,585,350 · 13 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
1w02w13w26w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x17cc5ec3…ae0e
0x34b655…2a6f
6 touches
3 conflicts
0x807bf45f…5016
0x34b655…2a6f
6 touches
3 conflicts
0x2447fab0…811d
0x34b655…2a6f
4 touches
1 conflict
0x25329a48…4e00
0x34b655…2a6f
4 touches
1 conflict
0x30278615…7ac6
0x34b655…2a6f
4 touches
1 conflict
0x366c7d57…0ed1
0x34b655…2a6f
4 touches
1 conflict
0x3be29374…1df9
0x34b655…2a6f
4 touches
1 conflict
0x5da65b2f…d0a7
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 0x17cc5ec39e…57ae0e
Audit this contract →
← previous block·next block →recent activity