← previous blocknext block →recent activity
Analyzing
Block #87,496,892
45 transactions · 37 stateful · 2026-07-13 13:50:05 UTC
Parallelism
64/100
Blocked
70%
Avg conflicts / tx
2.13
Longest chain
16 deep
Execution timeline
did this block parallelize well?
view
block #87,496,892 · 45 txs across 16 waves · depth 16
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
wave w11
wave w12
wave w13
wave w14
wave w15
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w15w26w07w18w29w015w118w019w120w221w322w423w528w229w930w1031w1132w235w136w337w438w541w13
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
16 touches
28 conflicts
0x7b2f3e6d…978f
0x34b655…2a6f
12 touches
15 conflicts
0x092832cd…7b28
0x34b655…2a6f
10 touches
10 conflicts
0x326d4924…1788
0x34b655…2a6f
10 touches
10 conflicts
0x737acb78…fce8
0x34b655…2a6f
8 touches
6 conflicts
0x78b7945b…2113
0x34b655…2a6f
8 touches
6 conflicts
0x66f473d3…2d03
0xa6afd3…d132
8 touches
6 conflicts
0xf2f76ab3…623e
0x2a68ba…90c5
8 touches
6 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
28 conflicts on slot 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity