← previous blocknext block →recent activity

Analyzing

Block #74,383,130

25 transactions · 22 stateful · 2026-05-13 19:26:23 UTC

Parallelism

76/100

Blocked

45%

Avg conflicts / tx

0.72

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #74,383,130  ·  25 txs across 6 waves  ·  depth 6
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

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

0xd98b3c10…67b8

0x34b655…2a6f

8 touches
6 conflicts

0xa65e26c7…b729

0xd32edf…ff58

7 touches
6 conflicts

0x00000000…001a

0x1b6862…e19c

6 touches
3 conflicts

0xcb45d9d6…cb82

0x1b6862…e19c

6 touches
3 conflicts

0x46356904…5ead

0x34b655…2a6f

4 touches
1 conflict

0x00000000…0012

0x1b6862…e19c

4 touches
1 conflict

0xb409e204…89ac

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: 0x34b6552d…112a6f

6 conflicts on slot 0xd98b3c102b…ca67b8

← previous block·next block →recent activity