← previous blocknext block →recent activity
Analyzing
Block #87,726,905
25 transactions · 21 stateful · 2026-07-14 15:29:17 UTC
Parallelism
72/100
Blocked
48%
Avg conflicts / tx
0.8
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #87,726,905 · 25 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
4w05w18w09w110w211w312w414w515w018w119w623w224w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
10 touches
10 conflicts
0xc4de6652…13f4
0x34b655…2a6f
8 touches
6 conflicts
0xafb8e71e…9285
0x34b655…2a6f
6 touches
3 conflicts
0xeeaba9d3…b491
0x34b655…2a6f
6 touches
3 conflicts
0xd11dcf4e…518f
0x34b655…2a6f
6 touches
3 conflicts
0x53bddbe8…2e5e
0x34b655…2a6f
5 touches
3 conflicts
0xaf498679…7732
0x34b655…2a6f
4 touches
1 conflict
0xbaf2476c…859d
0x34b655…2a6f
4 touches
1 conflict
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