← previous blocknext block →recent activity

Analyzing

Block #91,410,338

17 transactions · 15 stateful · 2026-07-29 18:03:36 UTC

Parallelism

76/100

Blocked

53%

Avg conflicts / tx

0.88

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #91,410,338  ·  17 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

0x00000000…0002

0x48cba2…b48b

8 touches
6 conflicts

0x889d5e90…929a

0x2a68ba…90c5

6 touches
3 conflicts

0x7e5ea60a…c4aa

0x34b655…2a6f

6 touches
3 conflicts

0xb9834665…e363

0x34b655…2a6f

6 touches
3 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0x915c095e…c1e5

0x2b46c0…1669

4 touches
1 conflict

0xcfe06a18…b5b5

0x2b46c0…1669

4 touches
1 conflict

0xd8fd2add…50fc

0x2b46c0…1669

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: 0x48cba278…e2b48b

6 conflicts on slot 0x0000000000…000002

← previous block·next block →recent activity