← previous blocknext block →recent activity
Analyzing
Block #87,611,434
20 transactions · 17 stateful · 2026-07-14 02:36:56 UTC
Parallelism
70/100
Blocked
65%
Avg conflicts / tx
1.3
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #87,611,434 · 20 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
1w02w13w06w17w28w39w410w512w213w315w416w319w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
10 touches
10 conflicts
0x745952b2…d90c
0x34b655…2a6f
10 touches
10 conflicts
0x5170a218…3a84
0xc8689a…ee79
6 touches
3 conflicts
0xa0af25f7…9129
0x34b655…2a6f
6 touches
3 conflicts
0xcd61f53c…04ec
0x34b655…2a6f
6 touches
3 conflicts
0xcef0e4b7…46bf
0x34b655…2a6f
6 touches
3 conflicts
0xd379a368…fea4
0x34b655…2a6f
6 touches
3 conflicts
0xdb7c435f…f490
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
10 conflicts on slot 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity