← previous blocknext block →recent activity

Analyzing

Block #74,915,503

18 transactions · 16 stateful · 2026-05-16 06:42:44 UTC

Parallelism

61/100

Blocked

38%

Avg conflicts / tx

0.83

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #74,915,503  ·  18 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

0x388e001a…7e04

0x34b655…2a6f

10 touches
10 conflicts

0xf853eb8e…4027

0x34b655…2a6f

10 touches
10 conflicts

0x96af6949…d7d2

0x34b655…2a6f

8 touches
6 conflicts

0x60f7fbaf…bd58

0x34b655…2a6f

8 touches
6 conflicts

0xc6417de0…2191

0xc8689a…ee79

6 touches
3 conflicts

0x0711ec2d…d973

0x34b655…2a6f

6 touches
3 conflicts

0x65c65d77…bbd4

0x34b655…2a6f

6 touches
3 conflicts

0x8db1e0f2…2fcf

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: 0x34b6552d…112a6f

10 conflicts on slot 0x388e001a16…e57e04

← previous block·next block →recent activity