← previous blocknext block →recent activity

Analyzing

Block #90,534,882

19 transactions · 17 stateful · 2026-07-26 16:37:03 UTC

Parallelism

74/100

Blocked

41%

Avg conflicts / tx

0.68

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #90,534,882  ·  19 txs across 5 waves  ·  depth 5
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

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

10 touches
10 conflicts

0x00966e54…7d1d

0x34b655…2a6f

4 touches
1 conflict

0x00bbd28c…e227

0x34b655…2a6f

4 touches
1 conflict

0x05c3bda4…de90

0x34b655…2a6f

4 touches
1 conflict

0x08c1b53c…7316

0x34b655…2a6f

4 touches
1 conflict

0x1a5d321d…a474

0x34b655…2a6f

4 touches
1 conflict

0x366748e9…1282

0x34b655…2a6f

4 touches
1 conflict

0x4c28216f…08da

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

10 conflicts on slot 0xd98b3c102b…ca67b8

← previous block·next block →recent activity