← previous blocknext block →recent activity

Analyzing

Block #91,096,962

16 transactions · 12 stateful · 2026-07-28 15:45:45 UTC

Parallelism

81/100

Blocked

33%

Avg conflicts / tx

0.38

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #91,096,962  ·  16 txs across 3 waves  ·  depth 3
parallel ↔ serial

wave w0

wave w1

wave w2

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

0x0a0cecef…4ed0

0x34b655…2a6f

6 touches
3 conflicts

0xf4f9cac7…fd98

0x34b655…2a6f

4 touches
1 conflict

0xea02471d…1542

0x34b655…2a6f

4 touches
1 conflict

0xf3d10975…0d07

0x34b655…2a6f

4 touches
1 conflict

0x16dd4651…e88f

0x34b655…2a6f

4 touches
1 conflict

0x2d651956…12e8

0x34b655…2a6f

4 touches
1 conflict

0x2ed336a4…72b1

0x34b655…2a6f

4 touches
1 conflict

0x324cb18b…bcc6

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 0x0a0cecef55…324ed0

← previous block·next block →recent activity