← previous blocknext block →recent activity

Analyzing

Block #74,419,195

29 transactions · 23 stateful · 2026-05-13 23:26:24 UTC

Parallelism

69/100

Blocked

52%

Avg conflicts / tx

1.24

Longest chain

9 deep

Execution timeline

did this block parallelize well?

view

block #74,419,195  ·  29 txs across 9 waves  ·  depth 9
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

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

0x5603bbf6…ac4e

0xd32edf…ff58

13 touches
21 conflicts

0x00000000…003d

0x065c9d…c394

10 touches
10 conflicts

0xc3c8642a…7da5

0x2a68ba…90c5

8 touches
6 conflicts

0x819370a3…94ec

0x065c9d…c394

8 touches
6 conflicts

0x00000000…0013

0x1b6862…e19c

8 touches
6 conflicts

0x00000000…0015

0x1b6862…e19c

8 touches
6 conflicts

0xebde29d9…573c

0x1b6862…e19c

8 touches
6 conflicts

0xffe431af…8faa

0x065c9d…c394

6 touches
3 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: 0xd32edf66…9fff58

21 conflicts on slot 0x5603bbf6d2…24ac4e

← previous block·next block →recent activity