← previous blocknext block →recent activity

Analyzing

Block #74,307,572

16 transactions · 12 stateful · 2026-05-13 11:03:45 UTC

Parallelism

69/100

Blocked

50%

Avg conflicts / tx

0.81

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #74,307,572  ·  16 txs across 5 waves  ·  depth 5
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

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

0x9f1cb0a4…f2ce

0xd32edf…ff58

9 touches
10 conflicts

0x4d3e58e0…a2d7

0x34b655…2a6f

4 touches
1 conflict

0xd98b3c10…67b8

0x34b655…2a6f

4 touches
1 conflict

0xbbee74c2…567a

0x065c9d…c394

4 touches
1 conflict

0xd8bfeb1c…5426

0x065c9d…c394

3 touches
1 conflict

0x00000000…0019

0x1b6862…e19c

2 touches
0 conflicts

0x00000000…0029

0x1b6862…e19c

2 touches
0 conflicts

0xd9f18d9a…141d

0x1b6862…e19c

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: 0xd32edf66…9fff58

10 conflicts on slot 0x9f1cb0a46a…faf2ce

← previous block·next block →recent activity