← previous blocknext block →recent activity

Analyzing

Block #88,157,036

25 transactions · 22 stateful · 2026-07-16 15:26:31 UTC

Parallelism

88/100

Blocked

23%

Avg conflicts / tx

0.28

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #88,157,036  ·  25 txs across 3 waves  ·  depth 3
parallel ↔ serial

wave w0

wave w1

wave w2

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

0xbcbf5d09…8bac

0x34b655…2a6f

6 touches
3 conflicts

0x889d5e90…929a

0x2a68ba…90c5

4 touches
1 conflict

0x009a7be4…0822

0x34b655…2a6f

4 touches
1 conflict

0x0d2e1791…c1dd

0x34b655…2a6f

4 touches
1 conflict

0x1966c07e…fd4b

0x34b655…2a6f

4 touches
1 conflict

0x3a7fb5b5…f0e5

0x34b655…2a6f

4 touches
1 conflict

0x45969332…8798

0x34b655…2a6f

4 touches
1 conflict

0x482471ad…122f

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 0xbcbf5d09a8…c68bac

← previous block·next block →recent activity