← previous blocknext block →recent activity

Analyzing

Block #74,399,765

17 transactions · 15 stateful · 2026-05-13 21:17:07 UTC

Parallelism

65/100

Blocked

47%

Avg conflicts / tx

1.06

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #74,399,765  ·  17 txs across 6 waves  ·  depth 6
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

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

10 touches
10 conflicts

0xa02838a3…bc54

0x34b655…2a6f

8 touches
6 conflicts

0x60f7fbaf…bd58

0x34b655…2a6f

6 touches
3 conflicts

0xa678cb89…4abd

0x34b655…2a6f

5 touches
3 conflicts

0x62d080e9…4a7c

0x34b655…2a6f

4 touches
1 conflict

0x9b36f19f…fa5a

0x34b655…2a6f

4 touches
1 conflict

0xe57fd50c…ed92

0x34b655…2a6f

4 touches
1 conflict

0xe5c0ee9b…c29b

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

10 conflicts on slot 0xd98b3c102b…ca67b8

← previous block·next block →recent activity