← previous blocknext block →recent activity
Analyzing
Block #87,709,282
17 transactions · 15 stateful · 2026-07-14 13:31:13 UTC
Parallelism
65/100
Blocked
47%
Avg conflicts / tx
1.06
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #87,709,282 · 17 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w16w07w18w29w310w411w515w016w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
12 touches
15 conflicts
0xf565ea1f…4245
0x34b655…2a6f
6 touches
3 conflicts
0x15190be9…97ec
0x34b655…2a6f
6 touches
3 conflicts
0x4560e5a8…b741
0x34b655…2a6f
6 touches
3 conflicts
0x51c7ed1a…4b3e
0x34b655…2a6f
6 touches
3 conflicts
0x67905f6e…02a1
0x34b655…2a6f
6 touches
3 conflicts
0x7837c02d…0965
0x34b655…2a6f
6 touches
3 conflicts
0xeeaba9d3…b491
0x34b655…2a6f
6 touches
3 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
15 conflicts on slot 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity