← previous blocknext block →recent activity
Analyzing
Block #87,589,917
26 transactions · 25 stateful · 2026-07-14 00:13:03 UTC
Parallelism
62/100
Blocked
64%
Avg conflicts / tx
2.12
Longest chain
10 deep
Execution timeline
did this block parallelize well?
view
block #87,589,917 · 26 txs across 10 waves · depth 10
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w04w15w06w17w28w39w410w511w614w721w522w8
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa6b89ebb…a66e
0x34b655…2a6f
18 touches
36 conflicts
0xeeaba9d3…b491
0x34b655…2a6f
14 touches
21 conflicts
0xf1d76dba…4de3
0x34b655…2a6f
14 touches
21 conflicts
0x201679bc…0414
0x34b655…2a6f
14 touches
21 conflicts
0x21c9fd73…dae4
0x34b655…2a6f
14 touches
21 conflicts
0x34d95d94…3a16
0x34b655…2a6f
14 touches
21 conflicts
0x67905f6e…02a1
0x34b655…2a6f
14 touches
21 conflicts
0xac6f24e7…c98b
0x34b655…2a6f
14 touches
21 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
36 conflicts on slot 0xa6b89ebbaf…5fa66e
Audit this contract →
← previous block·next block →recent activity