← previous blocknext block →recent activity

Analyzing

Block #74,389,243

14 transactions · 11 stateful · 2026-05-13 20:07:03 UTC

Parallelism

79/100

Blocked

27%

Avg conflicts / tx

0.29

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #74,389,243  ·  14 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

0x00000000…003d

0x065c9d…c394

6 touches
3 conflicts

0x00000000…0002

0xab3526…fa38

4 touches
1 conflict

0x0b000000…0002

0x000000…1000

2 touches
0 conflicts

0x1628c457…21da

0x065c9d…c394

2 touches
0 conflicts

0x1be681c7…a3cb

0x065c9d…c394

2 touches
0 conflicts

0x48caaa1a…9076

0x065c9d…c394

2 touches
0 conflicts

0x4f8fcc1b…76e3

0x065c9d…c394

2 touches
0 conflicts

0xd4a120f8…7460

0x065c9d…c394

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: 0x065c9d28…a9c394

3 conflicts on slot 0x0000000000…00003d

← previous block·next block →recent activity