← previous blocknext block →recent activity
Analyzing
Block #87,496,660
38 transactions · 31 stateful · 2026-07-13 13:48:32 UTC
Parallelism
71/100
Blocked
65%
Avg conflicts / tx
2
Longest chain
11 deep
Execution timeline
did this block parallelize well?
view
block #87,496,660 · 38 txs across 11 waves · depth 11
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w14w25w06w17w08w19w010w011w116w218w319w420w521w622w723w824w927w428w629w730w834w935w1036w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
16 touches
28 conflicts
0xfdd655b8…bf89
0x34b655…2a6f
12 touches
15 conflicts
0xde696e46…6446
0x34b655…2a6f
10 touches
10 conflicts
0x42c7fd6d…fc6c
0x34b655…2a6f
8 touches
6 conflicts
0x4c188934…158e
0x34b655…2a6f
8 touches
6 conflicts
0x63c900f4…2600
0x34b655…2a6f
8 touches
6 conflicts
0x727fbce7…0c80
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
28 conflicts on slot 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity