← previous blocknext block →recent activity

Analyzing

Block #91,403,977

20 transactions · 18 stateful · 2026-07-29 17:31:22 UTC

Parallelism

75/100

Blocked

56%

Avg conflicts / tx

0.65

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #91,403,977  ·  20 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

0x43fd3667…094b

0x34b655…2a6f

6 touches
3 conflicts

0xa779293b…5e59

0x34b655…2a6f

6 touches
3 conflicts

0x41469894…598f

0x34b655…2a6f

4 touches
1 conflict

0x41469894…5990

0x34b655…2a6f

4 touches
1 conflict

0x482471ad…122f

0x34b655…2a6f

4 touches
1 conflict

0x4b99a706…8d0d

0x34b655…2a6f

4 touches
1 conflict

0x6e6b8ec7…2197

0x34b655…2a6f

4 touches
1 conflict

0x6fe7d366…78ff

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

3 conflicts on slot 0x43fd366775…d0094b

← previous block·next block →recent activity