← previous blocknext block →recent activity
Analyzing
Block #87,576,279
44 transactions · 37 stateful · 2026-07-13 22:41:50 UTC
Parallelism
66/100
Blocked
68%
Avg conflicts / tx
2.23
Longest chain
15 deep
Execution timeline
did this block parallelize well?
view
block #87,576,279 · 44 txs across 15 waves · depth 15
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w06w08w19w010w111w215w016w117w119w020w121w222w323w424w525w626w731w933w1135w1236w338w340w13
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
18 touches
36 conflicts
0x558fd353…1c6b
0x34b655…2a6f
10 touches
10 conflicts
0x702cd11f…652b
0x34b655…2a6f
10 touches
10 conflicts
0x0733be30…112f
0x34b655…2a6f
8 touches
6 conflicts
0x54b193ad…c830
0x34b655…2a6f
8 touches
6 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
8 touches
6 conflicts
0x8252706a…7ca5
0x34b655…2a6f
8 touches
6 conflicts
0xd92a03c7…bfc7
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