← previous blocknext block →recent activity
Analyzing
Block #87,513,292
43 transactions · 30 stateful · 2026-07-13 15:39:52 UTC
Parallelism
70/100
Blocked
67%
Avg conflicts / tx
1.81
Longest chain
13 deep
Execution timeline
did this block parallelize well?
view
block #87,513,292 · 43 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
1w02w04w05w16w28w09w111w119w020w121w222w323w424w525w626w727w830w733w935w139w1040w11
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
18 touches
36 conflicts
0x734ee320…caae
0x34b655…2a6f
10 touches
10 conflicts
0x4c04ce68…d007
0x34b655…2a6f
10 touches
10 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0x7c46fde6…d6a0
0x34b655…2a6f
8 touches
6 conflicts
0x69ce640b…884a
0x34b655…2a6f
8 touches
6 conflicts
0x59164e7a…7e0a
0x34b655…2a6f
6 touches
3 conflicts
0x737acb78…fce8
0x34b655…2a6f
6 touches
3 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