← previous blocknext block →recent activity
Analyzing
Block #87,259,040
29 transactions · 26 stateful · 2026-07-12 11:19:35 UTC
Parallelism
55/100
Blocked
77%
Avg conflicts / tx
2.38
Longest chain
13 deep
Execution timeline
did this block parallelize well?
view
block #87,259,040 · 29 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
1w02w14w05w17w08w19w210w311w412w513w614w715w817w118w419w521w622w223w325w927w11
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfaef08b1…0696
0x34b655…2a6f
18 touches
36 conflicts
0x96b8889e…9eac
0x34b655…2a6f
10 touches
10 conflicts
0xcfa965cc…6fcf
0x34b655…2a6f
10 touches
10 conflicts
0x4327afd2…1b3a
0x34b655…2a6f
8 touches
6 conflicts
0x49f6ddba…b7de
0x34b655…2a6f
8 touches
6 conflicts
0x727fbce7…0c80
0x34b655…2a6f
8 touches
6 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
8 touches
6 conflicts
0x7e5ea60a…c4ab
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
36 conflicts on slot 0xfaef08b108…f90696
Audit this contract →
← previous block·next block →recent activity