← previous blocknext block →recent activity

Analyzing

Block #90,026,495

18 transactions · 17 stateful · 2026-07-24 21:39:44 UTC

Parallelism

89/100

Blocked

18%

Avg conflicts / tx

0.17

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #90,026,495  ·  18 txs across 2 waves  ·  depth 2
parallel ↔ serial

wave w0

wave w1

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

0x2e9d65ac…2265

0x34b655…2a6f

4 touches
1 conflict

0x3e6302c8…64f5

0x34b655…2a6f

4 touches
1 conflict

0x86c98782…f3b7

0x34b655…2a6f

4 touches
1 conflict

0xc824469a…641f

0x34b655…2a6f

4 touches
1 conflict

0xc8d59e0f…cfe0

0x34b655…2a6f

4 touches
1 conflict

0xd98b3c10…67b8

0x34b655…2a6f

4 touches
1 conflict

0x6f58168d…ea24

0x34b655…2a6f

4 touches
1 conflict

0x889d5e90…929a

0x2a68ba…90c5

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

1 conflict on slot 0x2e9d65acda…142265

← previous block·next block →recent activity