← previous blocknext block →recent activity
Analyzing
Block #87,497,834
83 transactions · 53 stateful · 2026-07-13 13:56:23 UTC
Parallelism
72/100
Blocked
70%
Avg conflicts / tx
3.51
Longest chain
23 deep
Execution timeline
did this block parallelize well?
view
block #87,497,834 · 83 txs across 23 waves · depth 23
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w07w08w110w212w314w416w517w618w770w871w272w374w9
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
40 touches
190 conflicts
0x0da39371…1ecd
0x34b655…2a6f
20 touches
45 conflicts
0xd5dbfacf…c5ec
0x34b655…2a6f
18 touches
36 conflicts
0x889d5e90…929a
0x2a68ba…90c5
16 touches
28 conflicts
0x3eaeff71…ce55
0x34b655…2a6f
16 touches
28 conflicts
0x69411fb3…e36d
0x34b655…2a6f
16 touches
28 conflicts
0x73b0275e…82e9
0x34b655…2a6f
16 touches
28 conflicts
0xa60eabc0…9f8c
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
190 conflicts on slot 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity