← previous blocknext block →recent activity

Analyzing

Block #74,257,889

11 transactions · 7 stateful · 2026-05-13 05:33:14 UTC

Parallelism

64/100

Blocked

43%

Avg conflicts / tx

0.36

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #74,257,889  ·  11 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

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0xe89d3436…8088

0x34b655…2a6f

4 touches
1 conflict

0xf6476f21…3580

0x34b655…2a6f

4 touches
1 conflict

0xfd784183…67bb

0x34b655…2a6f

4 touches
1 conflict

0xb4b699c3…996b

0x34b655…2a6f

4 touches
1 conflict

0xb9d2cf20…a668

0x34b655…2a6f

4 touches
1 conflict

0x0c1aa307…ff9c

0x34b655…2a6f

2 touches
0 conflicts

0x132922df…c817

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

3 conflicts on slot 0xd98b3c102b…ca67b8

← previous block·next block →recent activity