← previous blocknext block →recent activity
Analyzing
Block #87,716,089
38 transactions · 30 stateful · 2026-07-14 14:16:51 UTC
Parallelism
71/100
Blocked
60%
Avg conflicts / tx
1.5
Longest chain
11 deep
Execution timeline
did this block parallelize well?
view
block #87,716,089 · 38 txs across 11 waves · depth 11
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w04w15w06w19w211w212w313w414w515w616w717w819w624w735w936w10
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
14 touches
21 conflicts
0x94ba9c4a…41d8
0x34b655…2a6f
8 touches
6 conflicts
0x74fd0a9b…3aaa
0x34b655…2a6f
8 touches
6 conflicts
0x8b818135…eff8
0x34b655…2a6f
8 touches
6 conflicts
0x22e0cc1d…ad07
0x34b655…2a6f
6 touches
3 conflicts
0x4de9cc37…2aba
0x34b655…2a6f
6 touches
3 conflicts
0x7fa1794c…3323
0x34b655…2a6f
6 touches
3 conflicts
0x7fe97198…79ab
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
21 conflicts on slot 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity