← previous blocknext block →recent activity

Analyzing

Block #73,386,644

13 transactions · 11 stateful · 2026-05-09 04:36:58 UTC

Parallelism

85/100

Blocked

18%

Avg conflicts / tx

0.23

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #73,386,644  ·  13 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

0x22e295f5…1bef

0x065c9d…c394

4 touches
1 conflict

0xe038916c…b1be

0x2a68ba…90c5

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0xbc425c5e…d286

0x065c9d…c394

3 touches
1 conflict

0x20212275…fee7

0xd32edf…ff58

3 touches
1 conflict

0xc5836f37…a2f5

0x065c9d…c394

2 touches
0 conflicts

0xf3e9e2d2…89ce

0x065c9d…c394

2 touches
0 conflicts

0x09000000…0001

0x000000…1000

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 0x22e295f5d8…ac1bef

← previous block·next block →recent activity