← previous blocknext block →recent activity
Analyzing
Block #87,524,970
26 transactions · 20 stateful · 2026-07-13 16:58:33 UTC
Parallelism
81/100
Blocked
50%
Avg conflicts / tx
0.5
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #87,524,970 · 26 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
3w04w17w08w113w014w115w117w218w319w223w224w325w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7e5ea60a…c4ab
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x06406f77…c83a
0x34b655…2a6f
4 touches
1 conflict
0x0733be30…112f
0x34b655…2a6f
4 touches
1 conflict
0x0da39371…1ecd
0x34b655…2a6f
4 touches
1 conflict
0x0e52d81f…461e
0x34b655…2a6f
4 touches
1 conflict
0x1191dbf7…8e85
0x34b655…2a6f
4 touches
1 conflict
0x198bae6a…f31c
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 0x7e5ea60ab2…b0c4ab
Audit this contract →
← previous block·next block →recent activity