← previous blocknext block →recent activity
Analyzing
Block #87,595,805
22 transactions · 19 stateful · 2026-07-14 00:52:27 UTC
Parallelism
68/100
Blocked
42%
Avg conflicts / tx
0.68
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #87,595,805 · 22 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w36w47w58w69w617w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe5bb3628…e5f1
0x34b655…2a6f
10 touches
10 conflicts
0x26050074…6967
0x34b655…2a6f
8 touches
6 conflicts
0x2dfde2ed…8801
0x34b655…2a6f
8 touches
6 conflicts
0x53bddbe8…2e5e
0x34b655…2a6f
8 touches
6 conflicts
0x6fe7d366…78ff
0x34b655…2a6f
8 touches
6 conflicts
0x70040326…40e5
0x34b655…2a6f
8 touches
6 conflicts
0x5b145de0…367c
0xc8689a…ee79
8 touches
6 conflicts
0xd11dcf4e…518f
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
10 conflicts on slot 0xe5bb3628b5…71e5f1
Audit this contract →
← previous block·next block →recent activity