← previous blocknext block →recent activity

Analyzing

Block #74,455,311

10 transactions · 9 stateful · 2026-05-14 03:26:52 UTC

Parallelism

70/100

Blocked

33%

Avg conflicts / tx

0.4

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #74,455,311  ·  10 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…003d

0x065c9d…c394

6 touches
3 conflicts

0x00c0824e…5b7d

0x065c9d…c394

4 touches
1 conflict

0x62147975…cc1e

0x065c9d…c394

4 touches
1 conflict

0xffe431af…8faa

0x065c9d…c394

4 touches
1 conflict

0xc1825e0d…57a4

0x065c9d…c394

3 touches
1 conflict

0x11a6bdde…f92a

0x065c9d…c394

3 touches
1 conflict

0x0ba30d7d…f662

0x065c9d…c394

3 touches
1 conflict

0xf1ba318c…64d8

0x065c9d…c394

3 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: 0x065c9d28…a9c394

3 conflicts on slot 0x0000000000…00003d

← previous block·next block →recent activity