← previous blocknext block →recent activity

Analyzing

Block #74,352,086

18 transactions · 13 stateful · 2026-05-13 15:59:42 UTC

Parallelism

78/100

Blocked

38%

Avg conflicts / tx

0.44

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #74,352,086  ·  18 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

0x194ac52f…2d08

0xd32edf…ff58

7 touches
6 conflicts

0x01e7b865…6e6d

0x188d58…ea8e

4 touches
1 conflict

0x01e7b865…6e70

0x188d58…ea8e

4 touches
1 conflict

0x2c4cd916…38cb

0x188d58…ea8e

4 touches
1 conflict

0x2c4cd916…38cc

0x188d58…ea8e

4 touches
1 conflict

0x00000000…0012

0x1b6862…e19c

4 touches
1 conflict

0x00000000…0013

0x1b6862…e19c

4 touches
1 conflict

0x00000000…0015

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: 0xd32edf66…9fff58

6 conflicts on slot 0x194ac52f57…972d08

← previous block·next block →recent activity