← previous blocknext block →recent activity

Analyzing

Block #74,344,338

27 transactions · 24 stateful · 2026-05-13 15:08:14 UTC

Parallelism

85/100

Blocked

63%

Avg conflicts / tx

1

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #74,344,338  ·  27 txs across 4 waves  ·  depth 4
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

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

0x00000000…0002

0xab3526…fa38

8 touches
6 conflicts

0xffe431af…8faa

0x065c9d…c394

8 touches
6 conflicts

0x5c8c6ab6…dc36

0x065c9d…c394

6 touches
3 conflicts

0x60f7fbaf…bd58

0x34b655…2a6f

6 touches
3 conflicts

0x4d37fe15…3be6

0x065c9d…c394

6 touches
3 conflicts

0xf3981be5…2c47

0x34b655…2a6f

6 touches
3 conflicts

0xf6cc7de8…0b4a

0x3bd359…433a

6 touches
3 conflicts

0x00000000…0000

0x63e48b…53f2

6 touches
3 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: 0xab35264b…1cfa38

6 conflicts on slot 0x0000000000…000002

← previous block·next block →recent activity