← previous blocknext block →recent activity

Analyzing

Block #91,796,239

20 transactions · 17 stateful · 2026-07-31 02:25:51 UTC

Parallelism

70/100

Blocked

47%

Avg conflicts / tx

0.75

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #91,796,239  ·  20 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

0x737acb78…fce8

0x34b655…2a6f

10 touches
10 conflicts

0xac2a0273…721b

0x34b655…2a6f

8 touches
6 conflicts

0xd2d3fe13…b827

0x34b655…2a6f

6 touches
3 conflicts

0xd2d3fe13…b828

0x34b655…2a6f

6 touches
3 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0xe19cc98a…d8cf

0x34b655…2a6f

6 touches
3 conflicts

0x211d520a…bf67

0x34b655…2a6f

6 touches
3 conflicts

0xf294562d…8734

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

10 conflicts on slot 0x737acb7813…fafce8

← previous block·next block →recent activity