← previous blocknext block →recent activity

Analyzing

Block #74,733,867

12 transactions · 11 stateful · 2026-05-15 10:30:24 UTC

Parallelism

83/100

Blocked

9%

Avg conflicts / tx

0.08

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #74,733,867  ·  12 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

0x0a6c34ee…b907

0x065c9d…c394

3 touches
1 conflict

0x15f62432…7222

0x065c9d…c394

3 touches
1 conflict

0x0b000000…0002

0x000000…1000

2 touches
0 conflicts

0x00000000…003d

0x065c9d…c394

2 touches
0 conflicts

0x319eef8e…07dd

0x065c9d…c394

2 touches
0 conflicts

0xb4ac39bd…20e2

0x065c9d…c394

2 touches
0 conflicts

0xd8ced140…0eb2

0x065c9d…c394

2 touches
0 conflicts

0xf3d7a307…4d63

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

1 conflict on slot 0x0a6c34eead…3ab907

← previous block·next block →recent activity