← previous blocknext block →recent activity
Analyzing
Block #87,407,875
38 transactions · 34 stateful · 2026-07-13 03:54:50 UTC
Parallelism
58/100
Blocked
71%
Avg conflicts / tx
2.55
Longest chain
16 deep
Execution timeline
did this block parallelize well?
view
block #87,407,875 · 38 txs across 16 waves · depth 16
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
4w05w16w27w28w09w110w211w012w114w215w316w417w518w619w724w1230w231w1332w333w14
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfaef08b1…0696
0x34b655…2a6f
22 touches
55 conflicts
0xd1fe26e6…8d31
0x34b655…2a6f
10 touches
10 conflicts
0xda46a376…f6a6
0x34b655…2a6f
10 touches
10 conflicts
0x8a35acfb…d1ae
0xb1dbf0…c0d3
10 touches
10 conflicts
0x8a35acfb…d1ad
0xb1dbf0…c0d3
10 touches
10 conflicts
0x286711a5…b3bf
0x34b655…2a6f
8 touches
6 conflicts
0x63c900f4…2600
0x34b655…2a6f
8 touches
6 conflicts
0x70638c24…1553
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
55 conflicts on slot 0xfaef08b108…f90696
Audit this contract →
← previous block·next block →recent activity