← previous blocknext block →recent activity

Analyzing

Block #74,631,859

11 transactions · 9 stateful · 2026-05-14 23:09:45 UTC

Parallelism

82/100

Blocked

22%

Avg conflicts / tx

0.18

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #74,631,859  ·  11 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

0x30276c1c…47b4

0x2a68ba…90c5

4 touches
1 conflict

0x0ddd4e79…b3b7

0x065c9d…c394

3 touches
1 conflict

0x4dd2fdb1…6fb9

0xd32edf…ff58

3 touches
1 conflict

0x04c00b0b…d324

0x065c9d…c394

2 touches
0 conflicts

0x5c8c6ab6…dc36

0x065c9d…c394

2 touches
0 conflicts

0x67792526…80f9

0x065c9d…c394

2 touches
0 conflicts

0xa1b6c64b…2849

0x065c9d…c394

2 touches
0 conflicts

0xa976d19d…543c

0x065c9d…c394

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: 0x2a68ba18…8e90c5

1 conflict on slot 0x30276c1c08…7247b4

← previous block·next block →recent activity