← previous blocknext block →recent activity

Analyzing

Block #74,959,755

9 transactions · 7 stateful · 2026-05-16 11:39:05 UTC

Parallelism

56/100

Blocked

43%

Avg conflicts / tx

0.56

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #74,959,755  ·  9 txs across 4 waves  ·  depth 4
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

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

0x679f68fe…5201

0x34b655…2a6f

6 touches
3 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0x631b4113…baa9

0x34b655…2a6f

6 touches
3 conflicts

0xebadaba6…8cc5

0x34b655…2a6f

4 touches
1 conflict

0x3ee3b7af…f8a7

0x1efe02…37d6

2 touches
0 conflicts

0xcfb436a0…d36b

0x1efe02…37d6

2 touches
0 conflicts

0xee205fb8…6101

0x1efe02…37d6

2 touches
0 conflicts

0x00bac013…a28c

0x91b81b…6d56

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

3 conflicts on slot 0x679f68fe2a…0a5201

← previous block·next block →recent activity