← previous blocknext block →recent activity
Analyzing
Block #87,700,512
61 transactions · 42 stateful · 2026-07-14 12:32:22 UTC
Parallelism
77/100
Blocked
60%
Avg conflicts / tx
1.15
Longest chain
14 deep
Execution timeline
did this block parallelize well?
view
block #87,700,512 · 61 txs across 14 waves · depth 14
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w05w06w08w19w011w112w120w021w122w223w324w425w026w132w033w134w237w338w439w540w646w250w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
16 touches
28 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
12 touches
15 conflicts
0x889d5e90…929a
0x2a68ba…90c5
10 touches
10 conflicts
0x5906754f…b584
0x34b655…2a6f
6 touches
3 conflicts
0x6e1cd42e…1f23
0x34b655…2a6f
6 touches
3 conflicts
0x0dbf9688…c6cf
0xd18b7e…414b
6 touches
3 conflicts
0x427d1120…4eb1
0x34b655…2a6f
6 touches
3 conflicts
0x4b90e63c…c17d
0x34b655…2a6f
6 touches
3 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