← previous blocknext block →recent activity

Analyzing

Block #74,454,431

24 transactions · 11 stateful · 2026-05-14 03:20:59 UTC

Parallelism

88/100

Blocked

36%

Avg conflicts / tx

0.21

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #74,454,431  ·  24 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

0x00000000…0013

0x1b6862…e19c

6 touches
3 conflicts

0x91945265…e58e

0x1b6862…e19c

6 touches
3 conflicts

0x00000000…0015

0x1b6862…e19c

6 touches
3 conflicts

0x9e73d994…1b9d

0xd32edf…ff58

5 touches
3 conflicts

0x00000000…001b

0x1b6862…e19c

4 touches
1 conflict

0x00000000…0012

0x1b6862…e19c

4 touches
1 conflict

0xd9f18d9a…141d

0x1b6862…e19c

4 touches
1 conflict

0x8876d94c…8435

0x2a68ba…90c5

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: 0x1b68626d…2de19c

3 conflicts on slot 0x0000000000…000013

← previous block·next block →recent activity