← previous blocknext block →recent activity

Analyzing

Block #91,277,455

20 transactions · 17 stateful · 2026-07-29 06:54:33 UTC

Parallelism

75/100

Blocked

47%

Avg conflicts / tx

0.6

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #91,277,455  ·  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…004c

0x80c745…7210

6 touches
3 conflicts

0x5502e1cc…3910

0x34b655…2a6f

6 touches
3 conflicts

0x737acb78…fce8

0x34b655…2a6f

6 touches
3 conflicts

0xac2a0273…721b

0x34b655…2a6f

6 touches
3 conflicts

0x00000000…004b

0x80c745…7210

6 touches
3 conflicts

0x5af098c7…4806

0x34b655…2a6f

4 touches
1 conflict

0x5af098c7…4807

0x34b655…2a6f

4 touches
1 conflict

0x5b4ca0c3…fdb4

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: 0x80c74517…647210

3 conflicts on slot 0x0000000000…00004c

← previous block·next block →recent activity