← previous blocknext block →recent activity

Analyzing

Block #91,439,436

15 transactions · 15 stateful · 2026-07-29 20:30:56 UTC

Parallelism

73/100

Blocked

47%

Avg conflicts / tx

0.73

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #91,439,436  ·  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

0xe8eae8a3…bacc

0x34b655…2a6f

6 touches
3 conflicts

0x4c619b7d…f4fa

0x34b655…2a6f

6 touches
3 conflicts

0x00000000…004b

0x80c745…7210

6 touches
3 conflicts

0x00000000…004c

0x80c745…7210

6 touches
3 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0xacd1b162…bee6

0x34b655…2a6f

6 touches
3 conflicts

0x8b4a1f2c…7a52

0x34b655…2a6f

4 touches
1 conflict

0x935e0525…f741

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 0xe8eae8a323…64bacc

← previous block·next block →recent activity