← previous blocknext block →recent activity

Analyzing

Block #91,096,520

20 transactions · 19 stateful · 2026-07-28 15:43:31 UTC

Parallelism

55/100

Blocked

58%

Avg conflicts / tx

1.3

Longest chain

9 deep

Execution timeline

did this block parallelize well?

view

block #91,096,520  ·  20 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

10 touches
10 conflicts

0x6fe7d366…78ff

0x34b655…2a6f

8 touches
6 conflicts

0xcc58c80b…ff79

0x34b655…2a6f

6 touches
3 conflicts

0x40c5d5cc…d164

0x34b655…2a6f

4 touches
1 conflict

0x421099c9…8896

0x34b655…2a6f

4 touches
1 conflict

0x55d08ae4…42ec

0x34b655…2a6f

4 touches
1 conflict

0x737acb78…fce8

0x34b655…2a6f

4 touches
1 conflict

0x7e5ea60a…c4aa

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 0xd98b3c102b…ca67b8

← previous block·next block →recent activity