← previous blocknext block →recent activity

Analyzing

Block #73,338,995

9 transactions · 8 stateful · 2026-05-08 23:20:01 UTC

Parallelism

78/100

Blocked

13%

Avg conflicts / tx

0.11

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #73,338,995  ·  9 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

0xbd7e37a9…9eb5

0x065c9d…c394

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0xaa266e6f…a5e3

0x065c9d…c394

3 touches
1 conflict

0x161494df…8825

0x065c9d…c394

3 touches
1 conflict

0x4996a77b…12d3

0x065c9d…c394

3 touches
1 conflict

0x8a00a57c…4258

0x065c9d…c394

2 touches
0 conflicts

0x9b812173…be62

0x065c9d…c394

2 touches
0 conflicts

0xab4b6c67…fde9

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 0xbd7e37a9b5…859eb5

← previous block·next block →recent activity