← previous blocknext block →recent activity

Analyzing

Block #88,367,095

31 transactions · 29 stateful · 2026-07-17 14:52:48 UTC

Parallelism

61/100

Blocked

59%

Avg conflicts / tx

1.61

Longest chain

12 deep

Execution timeline

did this block parallelize well?

view

block #88,367,095  ·  31 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

0x6fe7d366…78ff

0x34b655…2a6f

12 touches
15 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

12 touches
15 conflicts

0x37d59c51…799d

0xd32edf…ff58

7 touches
6 conflicts

0x737acb78…fce8

0x34b655…2a6f

6 touches
3 conflicts

0xbdc80bf7…e947

0x34b655…2a6f

6 touches
3 conflicts

0xa0d3a786…91d9

0x34b655…2a6f

6 touches
3 conflicts

0xac2a0273…721b

0x34b655…2a6f

6 touches
3 conflicts

0x3ef0952c…762d

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