← previous blocknext block →recent activity

Analyzing

Block #74,369,673

16 transactions · 11 stateful · 2026-05-13 17:56:43 UTC

Parallelism

88/100

Blocked

9%

Avg conflicts / tx

0.06

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #74,369,673  ·  16 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

0xef5dc6a4…b487

0x065c9d…c394

3 touches
1 conflict

0x09000000…0007

0x000000…1000

2 touches
0 conflicts

0x0b000000…0002

0x000000…1000

2 touches
0 conflicts

0x47b807a2…3307

0x065c9d…c394

2 touches
0 conflicts

0x00000000…006f

0x1efe02…37d6

2 touches
0 conflicts

0xad417593…ba1e

0x1efe02…37d6

2 touches
0 conflicts

0xb1f46e2c…56d8

0x1efe02…37d6

2 touches
0 conflicts

0xd3c1a628…7120

0x1efe02…37d6

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

1 conflict on slot 0xef5dc6a4e8…2cb487

← previous block·next block →recent activity