← previous blocknext block →recent activity

Analyzing

Block #90,643,295

14 transactions · 11 stateful · 2026-07-27 01:42:26 UTC

Parallelism

86/100

Blocked

27%

Avg conflicts / tx

0.21

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #90,643,295  ·  14 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

0x22e0cc1d…ad0d

0x34b655…2a6f

4 touches
1 conflict

0xf9ac650a…d82d

0x34b655…2a6f

4 touches
1 conflict

0xd9a771df…a27b

0x34b655…2a6f

4 touches
1 conflict

0xd98b3c10…67b8

0x34b655…2a6f

4 touches
1 conflict

0x889d5e90…929a

0x2a68ba…90c5

4 touches
1 conflict

0xd67c8acb…4d0d

0x34b655…2a6f

4 touches
1 conflict

0x9f770824…da10

0x34b655…2a6f

4 touches
1 conflict

0x53cccb07…d7f0

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

1 conflict on slot 0x22e0cc1d4a…90ad0d

← previous block·next block →recent activity