← previous blocknext block →recent activity

Analyzing

Block #74,040,363

22 transactions · 17 stateful · 2026-05-12 05:26:14 UTC

Parallelism

86/100

Blocked

24%

Avg conflicts / tx

0.27

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #74,040,363  ·  22 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

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0xdee4bb42…c809

0xd32edf…ff58

5 touches
3 conflicts

0xdaca243a…f9de

0x34b655…2a6f

4 touches
1 conflict

0x070a562a…8147

0x34b655…2a6f

4 touches
1 conflict

0x38158d6c…e5d1

0x34b655…2a6f

4 touches
1 conflict

0x00000000…0005

0x0594c7…a3be

2 touches
0 conflicts

0x77d91bcc…277e

0x0594c7…a3be

2 touches
0 conflicts

0x87d3dbaf…a010

0x0594c7…a3be

2 touches
0 conflicts

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

3 conflicts on slot 0xd98b3c102b…ca67b8

← previous block·next block →recent activity