← previous blocknext block →recent activity

Analyzing

Block #74,247,684

7 transactions · 6 stateful · 2026-05-13 04:25:26 UTC

Parallelism

57/100

Blocked

33%

Avg conflicts / tx

0.29

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #74,247,684  ·  7 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

0xd98b3c10…67b8

0x34b655…2a6f

4 touches
1 conflict

0x768cffcd…2648

0x34b655…2a6f

4 touches
1 conflict

0xa3ff1ab2…8ae3

0x34b655…2a6f

4 touches
1 conflict

0x1bb36615…bef1

0x34b655…2a6f

2 touches
0 conflicts

0x2965e2d6…5800

0x34b655…2a6f

2 touches
0 conflicts

0x6c44331f…9735

0x34b655…2a6f

2 touches
0 conflicts

0x90662685…e667

0x34b655…2a6f

2 touches
0 conflicts

0xb8228d38…3953

0x34b655…2a6f

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 0xd98b3c102b…ca67b8

← previous block·next block →recent activity