← previous blocknext block →recent activity
Analyzing
Block #87,704,817
50 transactions · 48 stateful · 2026-07-14 13:01:20 UTC
Parallelism
72/100
Blocked
69%
Avg conflicts / tx
2.12
Longest chain
14 deep
Execution timeline
did this block parallelize well?
view
block #87,704,817 · 50 txs across 14 waves · depth 14
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w04w05w16w27w08w09w110w211w312w013w114w015w116w217w318w419w533w234w336w338w439w540w143w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
18 touches
36 conflicts
0x00000000…0001
0xc1ff9f…b0fc
12 touches
15 conflicts
0x43fab434…896f
0xa6afd3…d132
10 touches
10 conflicts
0xac2a0273…721b
0x34b655…2a6f
8 touches
6 conflicts
0x1fd19887…8e0e
0x34b655…2a6f
8 touches
6 conflicts
0x7a916b05…8a00
0x34b655…2a6f
8 touches
6 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
8 touches
6 conflicts
0x8fe37a3f…4c89
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 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity