← previous blocknext block →recent activity

Analyzing

Block #74,425,013

15 transactions · 11 stateful · 2026-05-14 00:05:09 UTC

Parallelism

73/100

Blocked

36%

Avg conflicts / tx

0.47

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #74,425,013  ·  15 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

0x8fb866d9…aa5e

0xd32edf…ff58

7 touches
6 conflicts

0x17606ba6…1b6e

0x754704…b603

4 touches
1 conflict

0x0b000000…0002

0x000000…1000

2 touches
0 conflicts

0x7f975651…8c28

0x0555e3…2b9c

2 touches
0 conflicts

0x57b13e84…0459

0x065c9d…c394

2 touches
0 conflicts

0xbbee74c2…567a

0x065c9d…c394

2 touches
0 conflicts

0x01e7b865…6e6d

0x188d58…ea8e

2 touches
0 conflicts

0x01e7b865…6e6f

0x188d58…ea8e

2 touches
0 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

6 conflicts on slot 0x8fb866d9bb…ecaa5e

← previous block·next block →recent activity