← previous blocknext block →recent activity

Analyzing

Block #91,101,885

21 transactions · 20 stateful · 2026-07-28 16:10:31 UTC

Parallelism

62/100

Blocked

50%

Avg conflicts / tx

1.14

Longest chain

8 deep

Execution timeline

did this block parallelize well?

view

block #91,101,885  ·  21 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

10 touches
10 conflicts

0x6fe7d366…78ff

0x34b655…2a6f

8 touches
6 conflicts

0x482471ad…122f

0x34b655…2a6f

8 touches
6 conflicts

0x1526b11f…8b21

0x34b655…2a6f

6 touches
3 conflicts

0x36a76bd2…1fb0

0x34b655…2a6f

4 touches
1 conflict

0x4a6b3039…6a98

0x34b655…2a6f

4 touches
1 conflict

0x599dbed7…e39c

0x34b655…2a6f

4 touches
1 conflict

0x6c3907cd…5ac0

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

10 conflicts on slot 0xc824469a90…af6425

← previous block·next block →recent activity