← previous blocknext block →recent activity

Analyzing

Block #91,395,627

22 transactions · 21 stateful · 2026-07-29 16:49:16 UTC

Parallelism

68/100

Blocked

43%

Avg conflicts / tx

0.68

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #91,395,627  ·  22 txs across 7 waves  ·  depth 7
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

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

0xd98b3c10…67b8

0x34b655…2a6f

8 touches
6 conflicts

0x30dc6215…f9d0

0xd32edf…ff58

7 touches
6 conflicts

0x261b18ac…d06d

0x34b655…2a6f

4 touches
1 conflict

0x4abfb389…18f4

0x34b655…2a6f

4 touches
1 conflict

0x6fbc2e5a…e69c

0x34b655…2a6f

4 touches
1 conflict

0x7b987499…a00c

0x34b655…2a6f

4 touches
1 conflict

0x86977b3d…a9c4

0x34b655…2a6f

4 touches
1 conflict

0x90a021f0…f922

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 0xd98b3c102b…ca67b8

← previous block·next block →recent activity