← previous blocknext block →recent activity
Analyzing
Block #87,731,769
87 transactions · 76 stateful · 2026-07-14 16:01:49 UTC
Parallelism
72/100
Blocked
80%
Avg conflicts / tx
5.43
Longest chain
24 deep
Execution timeline
did this block parallelize well?
view
block #87,731,769 · 87 txs across 24 waves · depth 24
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
wave w21
wave w22
wave w23
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w14w28w09w110w211w312w413w514w617w777w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
46 touches
253 conflicts
0xc824469a…6425
0x34b655…2a6f
24 touches
66 conflicts
0x00000000…0001
0xc1ff9f…b0fc
22 touches
55 conflicts
0x00000000…0002
0x04fdea…47d7
20 touches
45 conflicts
0x482471ad…122f
0x34b655…2a6f
18 touches
36 conflicts
0x00000000…00c9
0x34b655…2a6f
18 touches
36 conflicts
0x67905f6e…02a1
0x34b655…2a6f
16 touches
28 conflicts
0x805d08cf…3cfc
0x34b655…2a6f
16 touches
28 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
253 conflicts on slot 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity