← previous blocknext block →recent activity
Analyzing
Block #87,592,473
44 transactions · 36 stateful · 2026-07-14 00:30:08 UTC
Parallelism
61/100
Blocked
72%
Avg conflicts / tx
2.73
Longest chain
17 deep
Execution timeline
did this block parallelize well?
view
block #87,592,473 · 44 txs across 17 waves · depth 17
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
wave w16
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w38w09w011w116w017w118w219w320w421w522w623w724w825w926w134w335w436w537w638w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
24 touches
66 conflicts
0xd93edb3f…94ec
0x34b655…2a6f
14 touches
21 conflicts
0xe5bb3628…e5f1
0x34b655…2a6f
10 touches
10 conflicts
0x00000000…003d
0xa6afd3…d132
10 touches
10 conflicts
0x1750da27…5388
0x34b655…2a6f
10 touches
10 conflicts
0x1de49243…4aa3
0x34b655…2a6f
10 touches
10 conflicts
0x70040326…40e5
0x34b655…2a6f
8 touches
6 conflicts
0x7d7ff6bb…f729
0x34b655…2a6f
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
66 conflicts on slot 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity