← previous blocknext block →recent activity

Analyzing

Block #73,660,447

12 transactions · 9 stateful · 2026-05-10 11:01:31 UTC

Parallelism

83/100

Blocked

11%

Avg conflicts / tx

0.08

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #73,660,447  ·  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

0xb70c74e5…143d

0x065c9d…c394

4 touches
1 conflict

0xc9e97522…3519

0x2a68ba…90c5

4 touches
1 conflict

0x17606ba6…1b6e

0x754704…b603

4 touches
1 conflict

0xa1087a5c…66c4

0x754704…b603

4 touches
1 conflict

0x8e80434a…a96d

0x0555e3…2b9c

2 touches
0 conflicts

0x09beabbc…065c

0x188d58…ea8e

2 touches
0 conflicts

0x09beabbc…065d

0x188d58…ea8e

2 touches
0 conflicts

0x60b24061…7c23

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 0xb70c74e5d2…54143d

← previous block·next block →recent activity