← previous blocknext block →recent activity

Analyzing

Block #74,353,067

17 transactions · 13 stateful · 2026-05-13 16:06:14 UTC

Parallelism

71/100

Blocked

31%

Avg conflicts / tx

0.59

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #74,353,067  ·  17 txs across 5 waves  ·  depth 5
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

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

8 touches
6 conflicts

0x801a6e57…d85c

0x34b655…2a6f

8 touches
6 conflicts

0xbb12db23…857e

0x34b655…2a6f

5 touches
3 conflicts

0x35b65947…44d1

0xc8689a…ee79

4 touches
1 conflict

0x00456f78…2b80

0x34b655…2a6f

4 touches
1 conflict

0x2877f440…c2c8

0x34b655…2a6f

4 touches
1 conflict

0xb245fe36…d765

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

6 conflicts on slot 0xd98b3c102b…ca67b8

← previous block·next block →recent activity