← previous blocknext block →recent activity
Analyzing
Block #87,579,317
42 transactions · 36 stateful · 2026-07-13 23:02:09 UTC
Parallelism
71/100
Blocked
78%
Avg conflicts / tx
2.38
Longest chain
12 deep
Execution timeline
did this block parallelize well?
view
block #87,579,317 · 42 txs across 12 waves · depth 12
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w04w15w26w07w18w09w110w216w317w419w623w1024w1126w527w629w630w131w732w833w934w235w341w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
18 touches
36 conflicts
0x2d651956…12e8
0x34b655…2a6f
14 touches
21 conflicts
0xa5420e1f…3788
0x34b655…2a6f
12 touches
15 conflicts
0x4ca5fbf0…6059
0x34b655…2a6f
10 touches
10 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
10 touches
10 conflicts
0x00000000…0001
0xc1ff9f…b0fc
8 touches
6 conflicts
0x7e5ea60a…c4ab
0x34b655…2a6f
8 touches
6 conflicts
0xcc11c0f6…5670
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