← previous blocknext block →recent activity

Analyzing

Block #91,073,396

29 transactions · 19 stateful · 2026-07-28 13:47:06 UTC

Parallelism

79/100

Blocked

42%

Avg conflicts / tx

0.52

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #91,073,396  ·  29 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

8 touches
6 conflicts

0xac2a0273…721b

0x34b655…2a6f

8 touches
6 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

8 touches
6 conflicts

0xc824469a…6425

0x34b655…2a6f

6 touches
3 conflicts

0x1993f91a…d7e2

0x34b655…2a6f

4 touches
1 conflict

0x2385516f…eca5

0x34b655…2a6f

4 touches
1 conflict

0x31669291…b8bb

0x34b655…2a6f

4 touches
1 conflict

0x37359194…7740

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 0x737acb7813…fafce8

← previous block·next block →recent activity