← previous blocknext block →recent activity
Analyzing
Block #87,504,172
16 transactions · 15 stateful · 2026-07-13 14:38:48 UTC
Parallelism
69/100
Blocked
40%
Avg conflicts / tx
0.75
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #87,504,172 · 16 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w05w16w28w29w310w412w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x44e13e21…432d
0x34b655…2a6f
8 touches
6 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
8 touches
6 conflicts
0x326a02b5…8dad
0x34b655…2a6f
6 touches
3 conflicts
0x33dbd217…dad1
0x34b655…2a6f
4 touches
1 conflict
0x3b240736…242d
0x34b655…2a6f
4 touches
1 conflict
0x41e2ea73…ddf8
0x34b655…2a6f
4 touches
1 conflict
0x6fe7d366…78ff
0x34b655…2a6f
4 touches
1 conflict
0x7c9d8f66…dee0
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
6 conflicts on slot 0x44e13e2103…5d432d
Audit this contract →
← previous block·next block →recent activity