← previous blocknext block →recent activity

Analyzing

Block #88,351,678

23 transactions · 20 stateful · 2026-07-17 13:08:44 UTC

Parallelism

70/100

Blocked

40%

Avg conflicts / tx

0.78

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #88,351,678  ·  23 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

0xd98b3c10…67b8

0x34b655…2a6f

10 touches
10 conflicts

0x22e0cc1d…ad0d

0x34b655…2a6f

6 touches
3 conflicts

0xebac0f82…a49c

0x34b655…2a6f

6 touches
3 conflicts

0x120847e2…98c2

0x34b655…2a6f

6 touches
3 conflicts

0x6cfabf20…d256

0x34b655…2a6f

6 touches
3 conflicts

0x64a785e4…0110

0x34b655…2a6f

4 touches
1 conflict

0x6e1cd42e…1f23

0x34b655…2a6f

4 touches
1 conflict

0x76c4467d…ce28

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

10 conflicts on slot 0xd98b3c102b…ca67b8

← previous block·next block →recent activity