← previous blocknext block →recent activity

Analyzing

Block #88,351,588

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

Parallelism

45/100

Blocked

58%

Avg conflicts / tx

2.05

Longest chain

11 deep

Execution timeline

did this block parallelize well?

view

block #88,351,588  ·  20 txs across 11 waves  ·  depth 11
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

wave w9

wave w10

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

12 touches
15 conflicts

0xf565ea1f…4245

0x34b655…2a6f

10 touches
10 conflicts

0xac2a0273…721b

0x34b655…2a6f

10 touches
10 conflicts

0x737acb78…fce8

0x34b655…2a6f

8 touches
6 conflicts

0xfb874a6c…caa0

0x34b655…2a6f

8 touches
6 conflicts

0xebac0f82…a49c

0x34b655…2a6f

8 touches
6 conflicts

0xabb1c6c2…b883

0x34b655…2a6f

6 touches
3 conflicts

0x8e0e5570…445f

0x34b655…2a6f

6 touches
3 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

15 conflicts on slot 0xd98b3c102b…ca67b8

← previous block·next block →recent activity