← previous blocknext block →recent activity

Analyzing

Block #74,342,883

9 transactions · 8 stateful · 2026-05-13 14:58:34 UTC

Parallelism

56/100

Blocked

38%

Avg conflicts / tx

0.44

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #74,342,883  ·  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

0x2f7781d6…e632

0x34b655…2a6f

6 touches
3 conflicts

0xea02471d…1542

0x34b655…2a6f

6 touches
3 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0xf98e221c…ffe8

0x34b655…2a6f

4 touches
1 conflict

0x7c14c3db…11a8

0x34b655…2a6f

4 touches
1 conflict

0x97d5efed…1aa4

0x34b655…2a6f

4 touches
1 conflict

0xadac4a86…c2bc

0x34b655…2a6f

4 touches
1 conflict

0xe5e7089a…fb91

0x34b655…2a6f

4 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: 0x34b6552d…112a6f

3 conflicts on slot 0x2f7781d6c5…16e632

← previous block·next block →recent activity