← previous blocknext block →recent activity
Analyzing
Block #87,589,354
42 transactions · 38 stateful · 2026-07-14 00:09:17 UTC
Parallelism
69/100
Blocked
58%
Avg conflicts / tx
2.12
Longest chain
13 deep
Execution timeline
did this block parallelize well?
view
block #87,589,354 · 42 txs across 13 waves · depth 13
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w04w15w06w18w09w110w212w013w114w215w316w417w518w619w720w821w922w1023w1125w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
24 touches
66 conflicts
0x69c491e3…98d9
0x34b655…2a6f
10 touches
10 conflicts
0x201679bc…0414
0x34b655…2a6f
8 touches
6 conflicts
0x21c9fd73…dae4
0x34b655…2a6f
8 touches
6 conflicts
0x30c5329c…711c
0x34b655…2a6f
8 touches
6 conflicts
0x34d95d94…3a16
0x34b655…2a6f
8 touches
6 conflicts
0x38befc08…20c8
0x34b655…2a6f
8 touches
6 conflicts
0x3a6290da…e683
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
66 conflicts on slot 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity