← previous blocknext block →recent activity

Analyzing

Block #74,764,076

37 transactions · 29 stateful · 2026-05-15 13:52:19 UTC

Parallelism

81/100

Blocked

59%

Avg conflicts / tx

0.95

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #74,764,076  ·  37 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

0xef519bb8…17f4

0xd32edf…ff58

11 touches
15 conflicts

0xca0fef1c…b548

0x34b655…2a6f

8 touches
6 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

8 touches
6 conflicts

0xea02471d…1542

0x34b655…2a6f

8 touches
6 conflicts

0x60f7fbaf…bd58

0x34b655…2a6f

8 touches
6 conflicts

0x0b28bf77…e53a

0x34b655…2a6f

6 touches
3 conflicts

0x32ee90db…decc

0x34b655…2a6f

6 touches
3 conflicts

0x7b6d2deb…dde0

0x34b655…2a6f

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

15 conflicts on slot 0xef519bb838…c017f4

← previous block·next block →recent activity