← previous blocknext block →recent activity

Analyzing

Block #74,510,698

20 transactions · 18 stateful · 2026-05-14 09:36:12 UTC

Parallelism

65/100

Blocked

44%

Avg conflicts / tx

0.6

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #74,510,698  ·  20 txs across 7 waves  ·  depth 7
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

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

0xee2017ba…04a3

0xd32edf…ff58

7 touches
6 conflicts

0x5c8c6ab6…dc36

0x065c9d…c394

6 touches
3 conflicts

0x00000000…0013

0x1b6862…e19c

4 touches
1 conflict

0x00000000…0015

0x1b6862…e19c

4 touches
1 conflict

0xba5743c7…21c4

0x1b6862…e19c

4 touches
1 conflict

0x0872abbe…9c39

0x2a68ba…90c5

4 touches
1 conflict

0x765c236f…ff45

0x2a68ba…90c5

4 touches
1 conflict

0x8d0e98f3…7ba0

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

6 conflicts on slot 0xee2017ba92…b504a3

← previous block·next block →recent activity