← previous blocknext block →recent activity

Analyzing

Block #90,311,129

11 transactions · 11 stateful · 2026-07-25 21:38:52 UTC

Parallelism

45/100

Blocked

45%

Avg conflicts / tx

0.82

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #90,311,129  ·  11 txs across 6 waves  ·  depth 6
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

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

6 touches
3 conflicts

0xbcbf5d09…8bac

0x34b655…2a6f

6 touches
3 conflicts

0x3e1b21c6…b1e4

0x34b655…2a6f

4 touches
1 conflict

0x4147b177…c9ba

0x34b655…2a6f

4 touches
1 conflict

0x737acb78…fce8

0x34b655…2a6f

4 touches
1 conflict

0x81a169fb…d227

0x34b655…2a6f

4 touches
1 conflict

0x8e507257…71c1

0x34b655…2a6f

4 touches
1 conflict

0x9e70dadd…810d

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

← previous block·next block →recent activity