← previous blocknext block →recent activity

Analyzing

Block #74,510,961

23 transactions · 17 stateful · 2026-05-14 09:37:58 UTC

Parallelism

65/100

Blocked

47%

Avg conflicts / tx

1.26

Longest chain

8 deep

Execution timeline

did this block parallelize well?

view

block #74,510,961  ·  23 txs across 8 waves  ·  depth 8
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

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

0x00000000…0002

0xab3526…fa38

16 touches
28 conflicts

0x00000000…0000

0xeefbe0…1a09

4 touches
1 conflict

0x0b000000…0002

0x000000…1000

2 touches
0 conflicts

0x00000000…003d

0x065c9d…c394

2 touches
0 conflicts

0x40af5731…e38f

0x065c9d…c394

2 touches
0 conflicts

0x5c8c6ab6…dc36

0x065c9d…c394

2 touches
0 conflicts

0x9d1a81bd…344a

0x065c9d…c394

2 touches
0 conflicts

0x0872abbe…9c39

0x2a68ba…90c5

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: 0xab35264b…1cfa38

28 conflicts on slot 0x0000000000…000002

← previous block·next block →recent activity