← previous blocknext block →recent activity

Analyzing

Block #74,766,746

19 transactions · 11 stateful · 2026-05-15 14:10:15 UTC

Parallelism

89/100

Blocked

9%

Avg conflicts / tx

0.05

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #74,766,746  ·  19 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

0xf2c8ff9b…7edb

0x065c9d…c394

4 touches
1 conflict

0xa1087a5c…66c4

0x754704…b603

4 touches
1 conflict

0x30276c1c…47b4

0x2a68ba…90c5

4 touches
1 conflict

0x00f7e3b7…e015

0x188d58…ea8e

2 touches
0 conflicts

0x00f7e3b7…e016

0x188d58…ea8e

2 touches
0 conflicts

0x60b24061…7c23

0x188d58…ea8e

2 touches
0 conflicts

0x60b24061…7c24

0x188d58…ea8e

2 touches
0 conflicts

0xe75ce681…ba5f

0x188d58…ea8e

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 0xf2c8ff9b92…e07edb

← previous block·next block →recent activity