← previous blocknext block →recent activity

Analyzing

Block #91,973,119

19 transactions · 19 stateful · 2026-07-31 17:15:43 UTC

Parallelism

74/100

Blocked

37%

Avg conflicts / tx

0.84

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #91,973,119  ·  19 txs across 5 waves  ·  depth 5
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

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

0xc824469a…6425

0x34b655…2a6f

10 touches
10 conflicts

0x482471ad…122f

0x34b655…2a6f

8 touches
6 conflicts

0x31616f97…1acc

0x34b655…2a6f

8 touches
6 conflicts

0xc9c2f132…25f2

0x34b655…2a6f

8 touches
6 conflicts

0x0f2d78b1…7363

0x34b655…2a6f

6 touches
3 conflicts

0x34f42ea3…92c4

0x34b655…2a6f

6 touches
3 conflicts

0x5f60967a…8c2d

0x34b655…2a6f

6 touches
3 conflicts

0x7e5ea60a…c4aa

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 0xc824469a90…af6425

← previous block·next block →recent activity