← previous blocknext block →recent activity

Analyzing

Block #90,624,810

17 transactions · 14 stateful · 2026-07-27 00:09:26 UTC

Parallelism

82/100

Blocked

14%

Avg conflicts / tx

0.18

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #90,624,810  ·  17 txs across 3 waves  ·  depth 3
parallel ↔ serial

wave w0

wave w1

wave w2

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

0x4dee3f71…642a

0x34b655…2a6f

6 touches
3 conflicts

0x353a3a00…5e0a

0x34b655…2a6f

4 touches
1 conflict

0x36a76bd2…1fb0

0x34b655…2a6f

4 touches
1 conflict

0x868b0438…4d17

0x34b655…2a6f

4 touches
1 conflict

0xb5a3b1be…8122

0x34b655…2a6f

4 touches
1 conflict

0xd98b3c10…67b8

0x34b655…2a6f

4 touches
1 conflict

0xe5bb3628…e5f1

0x34b655…2a6f

4 touches
1 conflict

0x34d95d94…3a16

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 0x4dee3f71ec…bb642a

← previous block·next block →recent activity