← previous blocknext block →recent activity

Analyzing

Block #88,364,647

26 transactions · 17 stateful · 2026-07-17 14:36:09 UTC

Parallelism

73/100

Blocked

47%

Avg conflicts / tx

0.88

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #88,364,647  ·  26 txs across 7 waves  ·  depth 7
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

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

0x6fe7d366…78ff

0x34b655…2a6f

12 touches
15 conflicts

0xe5bb3628…e5f1

0x34b655…2a6f

6 touches
3 conflicts

0x2d651956…12e8

0x34b655…2a6f

6 touches
3 conflicts

0x1e166a45…98a7

0x34b655…2a6f

4 touches
1 conflict

0x260e71c7…f37a

0x34b655…2a6f

4 touches
1 conflict

0x482471ad…122f

0x34b655…2a6f

4 touches
1 conflict

0x5e7fe9f1…7b3b

0x34b655…2a6f

4 touches
1 conflict

0x6d9bea1c…2ca1

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

15 conflicts on slot 0x6fe7d366be…a578ff

← previous block·next block →recent activity