← previous blocknext block →recent activity
Analyzing
Block #88,157,091
22 transactions · 19 stateful · 2026-07-16 15:26:53 UTC
Parallelism
73/100
Blocked
37%
Avg conflicts / tx
0.68
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #88,157,091 · 22 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
2w04w06w07w18w29w310w414w117w418w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
10 touches
10 conflicts
0x634daab4…dd5e
0x34b655…2a6f
6 touches
3 conflicts
0x11772463…480e
0x34b655…2a6f
6 touches
3 conflicts
0x3d4584df…ffed
0x34b655…2a6f
4 touches
1 conflict
0x446e4f62…f7b6
0x34b655…2a6f
4 touches
1 conflict
0x5035fb14…dd41
0x34b655…2a6f
4 touches
1 conflict
0x5d77346a…863a
0x34b655…2a6f
4 touches
1 conflict
0x9e0787cd…9dfe
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
10 conflicts on slot 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity