← previous blocknext block →recent activity

Analyzing

Block #91,410,177

20 transactions · 19 stateful · 2026-07-29 18:02:48 UTC

Parallelism

75/100

Blocked

42%

Avg conflicts / tx

0.7

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #91,410,177  ·  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

0x00000000…0008

0x0ea966…0742

8 touches
6 conflicts

0x44ad89ba…cf83

0xe4f6e7…9657

8 touches
6 conflicts

0x724cd9ff…6684

0xe4f6e7…9657

8 touches
6 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

8 touches
6 conflicts

0x724cd9ff…6684

0x0cc9b2…7777

8 touches
6 conflicts

0x53cccb07…d7f0

0x34b655…2a6f

4 touches
1 conflict

0x74462c1e…84f3

0x34b655…2a6f

4 touches
1 conflict

0x7e1faa73…bfbf

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: 0x0ea96615…ff0742

6 conflicts on slot 0x0000000000…000008

← previous block·next block →recent activity