← previous blocknext block →recent activity

Analyzing

Block #91,087,126

20 transactions · 19 stateful · 2026-07-28 14:56:14 UTC

Parallelism

80/100

Blocked

37%

Avg conflicts / tx

0.5

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #91,087,126  ·  20 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

0xdd190722…ecae

0x34b655…2a6f

6 touches
3 conflicts

0x4c619b7d…f4fa

0x34b655…2a6f

4 touches
1 conflict

0x59e53875…fab0

0x34b655…2a6f

4 touches
1 conflict

0x6fe7d366…78ff

0x34b655…2a6f

4 touches
1 conflict

0x8047e9b2…9bb8

0x34b655…2a6f

4 touches
1 conflict

0x8b66399b…8d29

0x34b655…2a6f

4 touches
1 conflict

0x9aea124d…de52

0x34b655…2a6f

4 touches
1 conflict

0xb4e0a934…5fc7

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 0xdd190722b1…12ecae

← previous block·next block →recent activity