← previous blocknext block →recent activity

Analyzing

Block #91,970,431

25 transactions · 23 stateful · 2026-07-31 17:02:12 UTC

Parallelism

68/100

Blocked

48%

Avg conflicts / tx

1.2

Longest chain

8 deep

Execution timeline

did this block parallelize well?

view

block #91,970,431  ·  25 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

0xc824469a…6425

0x34b655…2a6f

12 touches
15 conflicts

0x482471ad…122f

0x34b655…2a6f

10 touches
10 conflicts

0xb96d00bc…8144

0x34b655…2a6f

10 touches
10 conflicts

0x4826d3fe…c99e

0x34b655…2a6f

8 touches
6 conflicts

0x427c9fc4…5cee

0x34b655…2a6f

8 touches
6 conflicts

0x2385516f…eca5

0x34b655…2a6f

6 touches
3 conflicts

0x31616f97…1acc

0x34b655…2a6f

6 touches
3 conflicts

0xb4fe4488…4b24

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

15 conflicts on slot 0xc824469a90…af6425

← previous block·next block →recent activity