← previous blocknext block →recent activity

Analyzing

Block #87,715,215

15 transactions · 13 stateful · 2026-07-14 14:10:58 UTC

Parallelism

73/100

Blocked

54%

Avg conflicts / tx

0.6

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #87,715,215  ·  15 txs across 4 waves  ·  depth 4
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others

Conflict graph

Blocked by

- write/write- - read/write

x = tx position · y = wave (depth)

Hot storage slots

Contention

0xbe9baf16…df37

0x34b655…2a6f

6 touches
3 conflicts

0x92385428…6941

0x34b655…2a6f

6 touches
3 conflicts

0x0ba865dd…a249

0x34b655…2a6f

4 touches
1 conflict

0x2385516f…eca5

0x34b655…2a6f

4 touches
1 conflict

0x2a6caf10…a93e

0x34b655…2a6f

4 touches
1 conflict

0x3d22c439…de6d

0x34b655…2a6f

4 touches
1 conflict

0x482471ad…122f

0x34b655…2a6f

4 touches
1 conflict

0x5d1ac445…5233

0x34b655…2a6f

4 touches
1 conflict

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

3 conflicts on slot 0xbe9baf16a9…e6df37

← previous block·next block →recent activity