← previous blocknext block →recent activity

Analyzing

Block #74,654,792

48 transactions · 28 stateful · 2026-05-15 01:42:39 UTC

Parallelism

83/100

Blocked

54%

Avg conflicts / tx

0.73

Longest chain

8 deep

Execution timeline

did this block parallelize well?

view

block #74,654,792  ·  48 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

0x167c3fd3…bc86

0xd32edf…ff58

11 touches
15 conflicts

0xbad68552…e6bf

0x34b655…2a6f

10 touches
10 conflicts

0x00000000…0013

0x1b6862…e19c

6 touches
3 conflicts

0x00000000…0015

0x1b6862…e19c

6 touches
3 conflicts

0x2eaef64d…7f82

0x34b655…2a6f

6 touches
3 conflicts

0xbbee74c2…567a

0x065c9d…c394

6 touches
3 conflicts

0xfa2527aa…9dd5

0x34b655…2a6f

6 touches
3 conflicts

0xfe3d37ee…6e67

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 0x167c3fd33a…66bc86

← previous block·next block →recent activity