← previous blocknext block →recent activity
Analyzing
Block #87,703,051
58 transactions · 44 stateful · 2026-07-14 12:49:27 UTC
Parallelism
67/100
Blocked
70%
Avg conflicts / tx
2.78
Longest chain
19 deep
Execution timeline
did this block parallelize well?
view
block #87,703,051 · 58 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
1w02w13w24w05w010w111w012w216w321w122w123w224w326w027w128w229w330w431w532w642w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
28 touches
91 conflicts
0x95c47f03…f1bb
0x34b655…2a6f
14 touches
21 conflicts
0xdfc21d7c…e062
0x34b655…2a6f
12 touches
15 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
10 touches
10 conflicts
0x92385428…6941
0x34b655…2a6f
10 touches
10 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
10 touches
10 conflicts
0x891ec24a…adfb
0xd32edf…ff58
9 touches
10 conflicts
0x10adf1bf…7b21
0x34b655…2a6f
8 touches
6 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
91 conflicts on slot 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity