← previous blocknext block →recent activity

Analyzing

Block #74,503,994

14 transactions · 13 stateful · 2026-05-14 08:51:01 UTC

Parallelism

79/100

Blocked

31%

Avg conflicts / tx

0.36

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #74,503,994  ·  14 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

0x60f7fbaf…bd58

0x34b655…2a6f

4 touches
1 conflict

0x0824c484…d962

0x3bd359…433a

4 touches
1 conflict

0x22f10271…841d

0x34b655…2a6f

2 touches
0 conflicts

0x4582e32d…1abe

0x34b655…2a6f

2 touches
0 conflicts

0x5303445f…8967

0x34b655…2a6f

2 touches
0 conflicts

0x65ff54af…aa01

0x34b655…2a6f

2 touches
0 conflicts

0x6d3780e3…0829

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