← previous blocknext block →recent activity

Analyzing

Block #88,354,721

23 transactions · 22 stateful · 2026-07-17 13:29:11 UTC

Parallelism

48/100

Blocked

55%

Avg conflicts / tx

1.78

Longest chain

12 deep

Execution timeline

did this block parallelize well?

view

block #88,354,721  ·  23 txs across 12 waves  ·  depth 12
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

wave w9

wave w10

wave w11

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

14 touches
21 conflicts

0x22e0cc1d…ad0d

0x34b655…2a6f

8 touches
6 conflicts

0x326a02b5…8dad

0x34b655…2a6f

8 touches
6 conflicts

0x482471ad…122f

0x34b655…2a6f

8 touches
6 conflicts

0xc824469a…6425

0x34b655…2a6f

8 touches
6 conflicts

0x0c9eb6ea…7c39

0x34b655…2a6f

8 touches
6 conflicts

0x7485bb0e…d1e0

0x34b655…2a6f

6 touches
3 conflicts

0x5866aa50…fe81

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

21 conflicts on slot 0xd98b3c102b…ca67b8

← previous block·next block →recent activity