← previous blocknext block →recent activity

Analyzing

Block #74,355,729

12 transactions · 9 stateful · 2026-05-13 16:23:58 UTC

Parallelism

67/100

Blocked

44%

Avg conflicts / tx

0.42

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #74,355,729  ·  12 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

0x2484cc15…5afc

0x34b655…2a6f

4 touches
1 conflict

0x00000000…0002

0xab3526…fa38

4 touches
1 conflict

0x8c49c85c…ee96

0x34b655…2a6f

4 touches
1 conflict

0x9e0e23b5…6910

0x34b655…2a6f

4 touches
1 conflict

0xaeb5864c…7679

0x2a68ba…90c5

2 touches
0 conflicts

0x1bde0d88…9fcf

0x34b655…2a6f

2 touches
0 conflicts

0x414e9446…4b59

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