← previous blocknext block →recent activity

Analyzing

Block #74,232,267

10 transactions · 7 stateful · 2026-05-13 02:42:55 UTC

Parallelism

80/100

Blocked

14%

Avg conflicts / tx

0.1

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #74,232,267  ·  10 txs across 2 waves  ·  depth 2
parallel ↔ serial

wave w0

wave w1

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

0xe6b3e0a7…d791

0xd32edf…ff58

3 touches
1 conflict

0x09000000…0007

0x000000…1000

2 touches
0 conflicts

0x0b000000…0002

0x000000…1000

2 touches
0 conflicts

0x00000000…003d

0x065c9d…c394

2 touches
0 conflicts

0x3c9c49cb…7b4c

0x065c9d…c394

2 touches
0 conflicts

0x5c0f1784…b56e

0x065c9d…c394

2 touches
0 conflicts

0x7df6a0e2…9c05

0x065c9d…c394

2 touches
0 conflicts

0x9453beb2…6f64

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

1 conflict on slot 0xe6b3e0a71c…39d791

← previous block·next block →recent activity