← previous blocknext block →recent activity
Analyzing
Block #87,517,938
39 transactions · 36 stateful · 2026-07-13 16:11:01 UTC
Parallelism
72/100
Blocked
61%
Avg conflicts / tx
1.67
Longest chain
11 deep
Execution timeline
did this block parallelize well?
view
block #87,517,938 · 39 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
1w02w03w14w26w07w19w010w111w112w213w314w415w516w617w718w825w328w129w230w632w334w735w8
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
16 touches
28 conflicts
0x99ee776a…053a
0x34b655…2a6f
10 touches
10 conflicts
0xa535ecc7…c0e0
0x34b655…2a6f
10 touches
10 conflicts
0xb1c67a7d…b9b1
0x34b655…2a6f
10 touches
10 conflicts
0xf4d1451d…a9f8
0x34b655…2a6f
10 touches
10 conflicts
0x63c900f4…2600
0x34b655…2a6f
10 touches
10 conflicts
0x83c94aa3…aa40
0x34b655…2a6f
8 touches
6 conflicts
0xad0c7701…1d83
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