← previous blocknext block →recent activity

Analyzing

Block #74,956,345

24 transactions · 22 stateful · 2026-05-16 11:16:04 UTC

Parallelism

67/100

Blocked

59%

Avg conflicts / tx

1.63

Longest chain

8 deep

Execution timeline

did this block parallelize well?

view

block #74,956,345  ·  24 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

0x9fa089e7…d6aa

0xd32edf…ff58

13 touches
21 conflicts

0x3e49348b…9445

0x34b655…2a6f

8 touches
6 conflicts

0x17606ba6…1b6e

0x754704…b603

8 touches
6 conflicts

0x00000000…001e

0x1b6862…e19c

6 touches
3 conflicts

0xcb45d9d6…cb86

0x1b6862…e19c

6 touches
3 conflicts

0xd9f18d9a…141d

0x1b6862…e19c

6 touches
3 conflicts

0x00000000…003d

0x065c9d…c394

6 touches
3 conflicts

0x348fda08…7e96

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 0x9fa089e7bf…26d6aa

← previous block·next block →recent activity