← previous blocknext block →recent activity

Analyzing

Block #74,775,781

32 transactions · 22 stateful · 2026-05-15 15:10:45 UTC

Parallelism

78/100

Blocked

59%

Avg conflicts / tx

0.91

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #74,775,781  ·  32 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

0xf1a6fc38…e90f

0xd32edf…ff58

11 touches
15 conflicts

0x00000000…003d

0x065c9d…c394

6 touches
3 conflicts

0xc13fac9b…d2d0

0x1b6862…e19c

6 touches
3 conflicts

0x348fda08…7e96

0x065c9d…c394

6 touches
3 conflicts

0x60f7fbaf…bd58

0x34b655…2a6f

6 touches
3 conflicts

0x00000000…0015

0x1b6862…e19c

6 touches
3 conflicts

0x00000000…0013

0x1b6862…e19c

6 touches
3 conflicts

0x5d5b27f4…e39c

0x754704…b603

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

15 conflicts on slot 0xf1a6fc3826…efe90f

← previous block·next block →recent activity