← previous blocknext block →recent activity
Analyzing
Block #87,699,837
73 transactions · 61 stateful · 2026-07-14 12:27:48 UTC
Parallelism
67/100
Blocked
77%
Avg conflicts / tx
4.44
Longest chain
24 deep
Execution timeline
did this block parallelize well?
view
block #87,699,837 · 73 txs across 24 waves · depth 24
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
wave w19
wave w20
wave w21
wave w22
wave w23
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w05w16w210w311w412w513w614w715w816w518w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
42 touches
210 conflicts
0x8cc1393f…07fb
0x34b655…2a6f
20 touches
45 conflicts
0x00000000…0002
0x04fdea…47d7
18 touches
36 conflicts
0xe6817f7e…fc4c
0xd32edf…ff58
17 touches
36 conflicts
0x6f6fc26c…3e34
0x34b655…2a6f
16 touches
28 conflicts
0x900900c7…0a3e
0x34b655…2a6f
16 touches
28 conflicts
0x767799cd…f423
0xc8689a…ee79
16 touches
28 conflicts
0xf37e83bd…84fa
0x34b655…2a6f
16 touches
28 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
210 conflicts on slot 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity