← previous blocknext block →recent activity

Analyzing

Block #87,723,108

27 transactions · 24 stateful · 2026-07-14 15:03:52 UTC

Parallelism

63/100

Blocked

58%

Avg conflicts / tx

1.85

Longest chain

10 deep

Execution timeline

did this block parallelize well?

view

block #87,723,108  ·  27 txs across 10 waves  ·  depth 10
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

wave w9

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

0x7525206c…fbd5

0x34b655…2a6f

16 touches
28 conflicts

0x6fe7d366…78ff

0x34b655…2a6f

16 touches
28 conflicts

0x67905f6e…02a1

0x34b655…2a6f

14 touches
21 conflicts

0x5b145de0…367c

0xc8689a…ee79

12 touches
15 conflicts

0x5e4b65e1…ebe1

0x34b655…2a6f

12 touches
15 conflicts

0x84d74093…7808

0x34b655…2a6f

12 touches
15 conflicts

0xeeaba9d3…b491

0x34b655…2a6f

12 touches
15 conflicts

0xc1a19598…404e

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 0x7525206cf5…dcfbd5

← previous block·next block →recent activity