← previous blocknext block →recent activity

Analyzing

Block #73,991,582

11 transactions · 10 stateful · 2026-05-12 00:00:44 UTC

Parallelism

82/100

Blocked

10%

Avg conflicts / tx

0.09

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #73,991,582  ·  11 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

0xf1259089…d38c

0x065c9d…c394

4 touches
1 conflict

0xf537eaa0…73c8

0x065c9d…c394

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0x524f48ea…ed1d

0x065c9d…c394

3 touches
1 conflict

0x866599d0…8bad

0x065c9d…c394

3 touches
1 conflict

0xd43ef8b2…0d15

0x065c9d…c394

2 touches
0 conflicts

0xdc82a7b4…6d5c

0x065c9d…c394

2 touches
0 conflicts

0xfe16a60f…4f08

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 0xf12590897b…d6d38c

← previous block·next block →recent activity