← previous blocknext block →recent activity

Analyzing

Block #74,359,889

21 transactions · 19 stateful · 2026-05-13 16:51:38 UTC

Parallelism

76/100

Blocked

42%

Avg conflicts / tx

0.81

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #74,359,889  ·  21 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

0xb00cfb9e…bb5c

0xd32edf…ff58

9 touches
10 conflicts

0x8c49c85c…ee96

0x34b655…2a6f

8 touches
6 conflicts

0x1952c598…df64

0x34b655…2a6f

6 touches
3 conflicts

0xea02471d…1542

0x34b655…2a6f

6 touches
3 conflicts

0xa8a37d9e…fdce

0x34b655…2a6f

4 touches
1 conflict

0xd5fee5ce…8358

0x34b655…2a6f

4 touches
1 conflict

0xd98b3c10…67b8

0x34b655…2a6f

4 touches
1 conflict

0xdf30b85a…4199

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: 0xd32edf66…9fff58

10 conflicts on slot 0xb00cfb9ef4…7abb5c

← previous block·next block →recent activity