← previous blocknext block →recent activity

Analyzing

Block #91,127,952

19 transactions · 18 stateful · 2026-07-28 18:21:39 UTC

Parallelism

68/100

Blocked

44%

Avg conflicts / tx

0.58

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #91,127,952  ·  19 txs across 6 waves  ·  depth 6
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

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

6 touches
3 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0x00000000…004c

0x80c745…7210

4 touches
1 conflict

0x40b02f96…4a15

0x34b655…2a6f

4 touches
1 conflict

0x5af098c7…4806

0x34b655…2a6f

4 touches
1 conflict

0x5af098c7…4807

0x34b655…2a6f

4 touches
1 conflict

0xa864f825…ce8c

0x34b655…2a6f

4 touches
1 conflict

0xb2195a0c…68ca

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

3 conflicts on slot 0x6fe7d366be…a578ff

← previous block·next block →recent activity