← previous blocknext block →recent activity
Analyzing
Block #87,512,789
21 transactions · 17 stateful · 2026-07-13 15:36:30 UTC
Parallelism
48/100
Blocked
59%
Avg conflicts / tx
1.81
Longest chain
11 deep
Execution timeline
did this block parallelize well?
view
block #87,512,789 · 21 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
1w06w17w28w39w410w511w613w714w818w9
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
12 touches
15 conflicts
0x734ee320…caae
0x34b655…2a6f
10 touches
10 conflicts
0x69ce640b…884a
0x34b655…2a6f
8 touches
6 conflicts
0xc514314c…1aa4
0x34b655…2a6f
8 touches
6 conflicts
0x8cf1f868…c5af
0x34b655…2a6f
8 touches
6 conflicts
0xa80684c9…3948
0x34b655…2a6f
8 touches
6 conflicts
0x737acb78…fce8
0x34b655…2a6f
6 touches
3 conflicts
0x98c8df6b…ec4d
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
15 conflicts on slot 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity