← previous blocknext block →recent activity
Analyzing
Block #87,503,777
80 transactions · 57 stateful · 2026-07-13 14:36:09 UTC
Parallelism
76/100
Blocked
68%
Avg conflicts / tx
2.08
Longest chain
19 deep
Execution timeline
did this block parallelize well?
view
block #87,503,777 · 80 txs across 19 waves · depth 19
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
wave w17
wave w18
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w04w19w010w212w313w115w016w117w218w320w021w126w261w563w364w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
20 touches
45 conflicts
0x7b2f3e6d…978f
0x34b655…2a6f
16 touches
28 conflicts
0x4cabb80a…46bf
0x34b655…2a6f
14 touches
21 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
12 touches
15 conflicts
0x9a36cb2e…0929
0x34b655…2a6f
10 touches
10 conflicts
0xa863a526…9995
0x34b655…2a6f
10 touches
10 conflicts
0xac2a0273…721b
0x34b655…2a6f
10 touches
10 conflicts
0xd0f6f4f2…dffa
0x34b655…2a6f
10 touches
10 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
45 conflicts on slot 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity