← previous blocknext block →recent activity
Analyzing
Block #87,512,808
73 transactions · 68 stateful · 2026-07-13 15:36:38 UTC
Parallelism
75/100
Blocked
72%
Avg conflicts / tx
4.18
Longest chain
18 deep
Execution timeline
did this block parallelize well?
view
block #87,512,808 · 73 txs across 18 waves · depth 18
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w14w09w010w111w212w314w415w516w617w754w259w160w262w163w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0001
0xc1ff9f…b0fc
36 touches
153 conflicts
0x6fe7d366…78ff
0x34b655…2a6f
20 touches
45 conflicts
0x00000000…0002
0x04fdea…47d7
16 touches
28 conflicts
0xe5a9274d…78d7
0x34b655…2a6f
14 touches
21 conflicts
0xfb4cb196…8c4a
0x34b655…2a6f
12 touches
15 conflicts
0xca2926e0…61b5
0x34b655…2a6f
12 touches
15 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
12 touches
15 conflicts
0x734ee320…caae
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: 0xc1ff9fef…f4b0fc
153 conflicts on slot 0x0000000000…000001
Audit this contract →
← previous block·next block →recent activity