← previous blocknext block →recent activity

Analyzing

Block #88,365,215

26 transactions · 24 stateful · 2026-07-17 14:40:00 UTC

Parallelism

77/100

Blocked

33%

Avg conflicts / tx

0.58

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #88,365,215  ·  26 txs across 6 waves  ·  depth 6
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

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

0x2d651956…12e8

0x34b655…2a6f

8 touches
6 conflicts

0x1e166a45…98a7

0x34b655…2a6f

6 touches
3 conflicts

0x0d377781…e5af

0x34b655…2a6f

4 touches
1 conflict

0x1951ee47…540f

0x34b655…2a6f

4 touches
1 conflict

0x00000000…0002

0x48cba2…b48b

4 touches
1 conflict

0x0c119c6d…a42e

0x34b655…2a6f

4 touches
1 conflict

0xd98b3c10…67b8

0x34b655…2a6f

4 touches
1 conflict

0xda27c764…7fab

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

6 conflicts on slot 0x2d65195682…4112e8

← previous block·next block →recent activity