← previous blocknext block →recent activity

Analyzing

Block #74,248,036

13 transactions · 11 stateful · 2026-05-13 04:27:47 UTC

Parallelism

85/100

Blocked

18%

Avg conflicts / tx

0.15

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #74,248,036  ·  13 txs across 2 waves  ·  depth 2
parallel ↔ serial

wave w0

wave w1

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

0x768cffcd…2648

0x34b655…2a6f

4 touches
1 conflict

0xd98b3c10…67b8

0x34b655…2a6f

4 touches
1 conflict

0x60f7fbaf…bd58

0x34b655…2a6f

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

2 touches
0 conflicts

0x0c2e71cf…f9f4

0x065c9d…c394

2 touches
0 conflicts

0x61c473f0…3054

0x065c9d…c394

2 touches
0 conflicts

0x6ab40054…f49c

0x065c9d…c394

2 touches
0 conflicts

0x7adf434f…1149

0x065c9d…c394

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

1 conflict on slot 0x768cffcdb0…d12648

← previous block·next block →recent activity