← previous blocknext block →recent activity

Analyzing

Block #73,922,611

6 transactions · 6 stateful · 2026-05-11 16:20:20 UTC

Parallelism

67/100

Blocked

17%

Avg conflicts / tx

0.17

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #73,922,611  ·  6 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

0xf537eaa0…73c8

0x065c9d…c394

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0x4a73dee8…f855

0x065c9d…c394

2 touches
0 conflicts

0x6397b980…94b8

0x065c9d…c394

2 touches
0 conflicts

0x6f08361d…bda6

0x065c9d…c394

2 touches
0 conflicts

0x82fbad67…6e7e

0x065c9d…c394

2 touches
0 conflicts

0x9e28ef36…3e36

0x065c9d…c394

2 touches
0 conflicts

0xc0c23ed3…70ab

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 0xf537eaa0c6…3873c8

← previous block·next block →recent activity