← previous blocknext block →recent activity

Analyzing

Block #91,423,475

20 transactions · 18 stateful · 2026-07-29 19:09:44 UTC

Parallelism

60/100

Blocked

56%

Avg conflicts / tx

1.3

Longest chain

8 deep

Execution timeline

did this block parallelize well?

view

block #91,423,475  ·  20 txs across 8 waves  ·  depth 8
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

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

12 touches
15 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0xd676e291…3ecf

0x34b655…2a6f

6 touches
3 conflicts

0xd4c76842…efcb

0x34b655…2a6f

6 touches
3 conflicts

0x5fdfa820…7b4b

0x34b655…2a6f

6 touches
3 conflicts

0x38c6ff01…689f

0x34b655…2a6f

6 touches
3 conflicts

0x8c3ca4bb…987b

0x34b655…2a6f

6 touches
3 conflicts

0x8eef368f…aa21

0x34b655…2a6f

6 touches
3 conflicts

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

15 conflicts on slot 0x6fe7d366be…a578ff

← previous block·next block →recent activity