← previous blocknext block →recent activity

Analyzing

Block #91,834,473

17 transactions · 16 stateful · 2026-07-31 05:38:12 UTC

Parallelism

76/100

Blocked

31%

Avg conflicts / tx

0.47

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #91,834,473  ·  17 txs across 4 waves  ·  depth 4
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

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

0x482471ad…122f

0x34b655…2a6f

8 touches
6 conflicts

0xc824469a…6425

0x34b655…2a6f

6 touches
3 conflicts

0x177211e2…1c2d

0x754704…b603

4 touches
1 conflict

0xc824469a…6426

0x34b655…2a6f

4 touches
1 conflict

0xcd1e3ac5…da86

0x34b655…2a6f

4 touches
1 conflict

0xcd93b2d2…30e6

0x34b655…2a6f

4 touches
1 conflict

0xfd42a6b9…4c81

0x34b655…2a6f

4 touches
1 conflict

0x1a3d2527…8ca0

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 0x482471adbb…39122f

← previous block·next block →recent activity