← previous blocknext block →recent activity

Analyzing

Block #91,151,855

16 transactions · 15 stateful · 2026-07-28 20:21:54 UTC

Parallelism

56/100

Blocked

60%

Avg conflicts / tx

1.19

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #91,151,855  ·  16 txs across 7 waves  ·  depth 7
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

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

0x6fe7d366…78ff

0x34b655…2a6f

12 touches
15 conflicts

0x1c91542b…f7b1

0x34b655…2a6f

4 touches
1 conflict

0x2d605961…113f

0x34b655…2a6f

4 touches
1 conflict

0x5fe7e126…6dd2

0x34b655…2a6f

4 touches
1 conflict

0xabbaaa99…0b4a

0x34b655…2a6f

4 touches
1 conflict

0xed59b1cd…8509

0x34b655…2a6f

4 touches
1 conflict

0x00000000…0002

0x48cba2…b48b

4 touches
1 conflict

0x0f2d78b1…7363

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

15 conflicts on slot 0x6fe7d366be…a578ff

← previous block·next block →recent activity