← previous blocknext block →recent activity

Analyzing

Block #91,208,833

15 transactions · 13 stateful · 2026-07-29 01:08:30 UTC

Parallelism

73/100

Blocked

46%

Avg conflicts / tx

0.67

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #91,208,833  ·  15 txs across 4 waves  ·  depth 4
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

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

0xc0eb79d1…29a4

0x34b655…2a6f

8 touches
6 conflicts

0xefcdf197…96a2

0x34b655…2a6f

6 touches
3 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0xba5ff1c3…4ff1

0x34b655…2a6f

6 touches
3 conflicts

0x4943c7e5…d013

0x34b655…2a6f

4 touches
1 conflict

0x4dda03d2…fe0d

0x34b655…2a6f

4 touches
1 conflict

0x636d143c…2ccb

0x34b655…2a6f

4 touches
1 conflict

0x6925548b…81cb

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

6 conflicts on slot 0xc0eb79d1cb…5529a4

← previous block·next block →recent activity