← previous blocknext block →recent activity

Analyzing

Block #91,070,205

23 transactions · 21 stateful · 2026-07-28 13:31:03 UTC

Parallelism

61/100

Blocked

43%

Avg conflicts / tx

1.26

Longest chain

9 deep

Execution timeline

did this block parallelize well?

view

block #91,070,205  ·  23 txs across 9 waves  ·  depth 9
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

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

0xd98b3c10…67b8

0x34b655…2a6f

14 touches
21 conflicts

0xf1345bef…5530

0x34b655…2a6f

6 touches
3 conflicts

0x424934c8…f2f1

0x34b655…2a6f

6 touches
3 conflicts

0x3e505a15…70f8

0x34b655…2a6f

4 touches
1 conflict

0x482471ad…122f

0x34b655…2a6f

4 touches
1 conflict

0x64ac7daf…c064

0x34b655…2a6f

4 touches
1 conflict

0x6dea4dbf…ba54

0x34b655…2a6f

4 touches
1 conflict

0x737acb78…fce8

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

21 conflicts on slot 0xd98b3c102b…ca67b8

← previous block·next block →recent activity