← previous blocknext block →recent activity

Analyzing

Block #74,248,347

9 transactions · 9 stateful · 2026-05-13 04:29:52 UTC

Parallelism

67/100

Blocked

33%

Avg conflicts / tx

0.44

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #74,248,347  ·  9 txs across 3 waves  ·  depth 3
parallel ↔ serial

wave w0

wave w1

wave w2

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

0x046a928e…0012

0x2a68ba…90c5

6 touches
3 conflicts

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0x04c38950…2f02

0x065c9d…c394

2 touches
0 conflicts

0x88660078…d658

0x065c9d…c394

2 touches
0 conflicts

0x8eaa9ffd…9abd

0x065c9d…c394

2 touches
0 conflicts

0x917ff916…7b90

0x065c9d…c394

2 touches
0 conflicts

0xc211d751…880c

0x065c9d…c394

2 touches
0 conflicts

0x00000000…0012

0x1b6862…e19c

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: 0x2a68ba18…8e90c5

3 conflicts on slot 0x046a928e85…e50012

← previous block·next block →recent activity