← previous blocknext block →recent activity

Analyzing

Block #91,978,001

18 transactions · 17 stateful · 2026-07-31 17:40:17 UTC

Parallelism

56/100

Blocked

59%

Avg conflicts / tx

1.33

Longest chain

8 deep

Execution timeline

did this block parallelize well?

view

block #91,978,001  ·  18 txs across 8 waves  ·  depth 8
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

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

10 touches
10 conflicts

0x9a3463f0…0b73

0x34b655…2a6f

8 touches
6 conflicts

0x35a9f06c…7689

0x34b655…2a6f

8 touches
6 conflicts

0xbffde283…3385

0x34b655…2a6f

8 touches
6 conflicts

0xc824469a…6425

0x34b655…2a6f

8 touches
6 conflicts

0x6f18d55f…758b

0x34b655…2a6f

6 touches
3 conflicts

0x482471ad…122f

0x34b655…2a6f

6 touches
3 conflicts

0x68ca40a2…bc7c

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 0xd98b3c102b…ca67b8

← previous block·next block →recent activity