← previous blocknext block →recent activity

Analyzing

Block #90,115,972

23 transactions · 21 stateful · 2026-07-25 05:13:25 UTC

Parallelism

57/100

Blocked

57%

Avg conflicts / tx

2.13

Longest chain

10 deep

Execution timeline

did this block parallelize well?

view

block #90,115,972  ·  23 txs across 10 waves  ·  depth 10
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

wave w9

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

0x724cd9ff…6684

0xe4f6e7…9657

20 touches
45 conflicts

0x724cd9ff…6684

0x0cc9b2…7777

20 touches
45 conflicts

0x00000000…0008

0x0ea966…0742

20 touches
45 conflicts

0x44ad89ba…cf83

0xe4f6e7…9657

20 touches
45 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0x96dd83e6…a507

0x34b655…2a6f

4 touches
1 conflict

0xb5cddf91…0abf

0x34b655…2a6f

4 touches
1 conflict

0xc824469a…6425

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: 0xe4f6e757…919657

45 conflicts on slot 0x724cd9ff19…4c6684

← previous block·next block →recent activity