← previous blocknext block →recent activity
Analyzing
Block #87,354,998
56 transactions · 39 stateful · 2026-07-12 22:01:09 UTC
Parallelism
63/100
Blocked
79%
Avg conflicts / tx
2.68
Longest chain
21 deep
Execution timeline
did this block parallelize well?
view
block #87,354,998 · 56 txs across 21 waves · depth 21
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
wave w19
wave w20
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
7w08w09w111w212w314w415w518w643w147w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfaef08b1…0696
0x34b655…2a6f
24 touches
66 conflicts
0x8cc1393f…07fb
0x34b655…2a6f
16 touches
28 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
14 touches
21 conflicts
0x7d64cfc8…6cd5
0x34b655…2a6f
12 touches
15 conflicts
0x2c8bf7d9…3cc7
0xc8689a…ee79
12 touches
15 conflicts
0x7b3da897…b268
0x34b655…2a6f
12 touches
15 conflicts
0x7cb2f3fa…4836
0x34b655…2a6f
12 touches
15 conflicts
0xa5fb4b5a…a120
0x34b655…2a6f
12 touches
15 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 0xfaef08b108…f90696
Audit this contract →
← previous block·next block →recent activity