← previous blocknext block →recent activity
Analyzing
Block #87,595,600
22 transactions · 20 stateful · 2026-07-14 00:51:04 UTC
Parallelism
50/100
Blocked
65%
Avg conflicts / tx
2.05
Longest chain
11 deep
Execution timeline
did this block parallelize well?
view
block #87,595,600 · 22 txs across 11 waves · depth 11
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w05w16w27w38w49w510w611w712w8
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
18 touches
36 conflicts
0x26050074…6967
0x34b655…2a6f
14 touches
21 conflicts
0x2dfde2ed…8801
0x34b655…2a6f
14 touches
21 conflicts
0x53bddbe8…2e5e
0x34b655…2a6f
14 touches
21 conflicts
0x5b145de0…367c
0xc8689a…ee79
14 touches
21 conflicts
0x7525d39c…213f
0x34b655…2a6f
14 touches
21 conflicts
0x9599eb41…b5d6
0x34b655…2a6f
14 touches
21 conflicts
0xd11dcf4e…518f
0x34b655…2a6f
14 touches
21 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
36 conflicts on slot 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity