← previous blocknext block →recent activity

Analyzing

Block #90,387,363

17 transactions · 16 stateful · 2026-07-26 04:08:53 UTC

Parallelism

71/100

Blocked

50%

Avg conflicts / tx

0.65

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #90,387,363  ·  17 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

0x50d44a56…fe50

0x34b655…2a6f

6 touches
3 conflicts

0x00000000…003d

0xa6afd3…d132

6 touches
3 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0xf5ea108a…dbf6

0x34b655…2a6f

6 touches
3 conflicts

0x424934c8…f2f1

0x34b655…2a6f

4 touches
1 conflict

0x525cb249…2e98

0x34b655…2a6f

4 touches
1 conflict

0x6127c8ac…3f6e

0x34b655…2a6f

4 touches
1 conflict

0x977e332f…fa36

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 0x50d44a5683…5afe50

← previous block·next block →recent activity