← previous blocknext block →recent activity

Analyzing

Block #74,338,694

13 transactions · 11 stateful · 2026-05-13 14:30:44 UTC

Parallelism

85/100

Blocked

27%

Avg conflicts / tx

0.23

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #74,338,694  ·  13 txs across 2 waves  ·  depth 2
parallel ↔ serial

wave w0

wave w1

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

0xc9a9747f…e622

0x34b655…2a6f

4 touches
1 conflict

0xf3981be5…2c47

0x34b655…2a6f

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0x5c8c6ab6…dc36

0x065c9d…c394

4 touches
1 conflict

0x8d33cfd5…d207

0x065c9d…c394

4 touches
1 conflict

0x8e5a3a82…d3c3

0x065c9d…c394

3 touches
1 conflict

0x6d3780e3…0829

0x34b655…2a6f

2 touches
0 conflicts

0x8b8e4020…11b0

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 0xc9a9747fe5…a6e622

← previous block·next block →recent activity