← previous blocknext block →recent activity

Analyzing

Block #74,284,136

14 transactions · 11 stateful · 2026-05-13 08:27:45 UTC

Parallelism

71/100

Blocked

55%

Avg conflicts / tx

0.5

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #74,284,136  ·  14 txs across 4 waves  ·  depth 4
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

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

0x60f7fbaf…bd58

0x34b655…2a6f

6 touches
3 conflicts

0x6b319071…a105

0xc8689a…ee79

4 touches
1 conflict

0x0d622e34…0000

0x681e90…ae09

4 touches
1 conflict

0xf853eb8e…4027

0x34b655…2a6f

4 touches
1 conflict

0x5de96bd3…c60c

0x34b655…2a6f

4 touches
1 conflict

0xd9f18d9a…141d

0x1b6862…e19c

4 touches
1 conflict

0x00000000…0012

0x1b6862…e19c

4 touches
1 conflict

0x00000000…0013

0x1b6862…e19c

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

3 conflicts on slot 0x60f7fbaf90…97bd58

← previous block·next block →recent activity