Block #73,987,367

← previous blocknext block →recent activity

Analyzing

Block #73,987,367

7 transactions · 6 stateful · 2026-05-11 23:32:14 UTC

Parallelism

57/100

Blocked

33%

Avg conflicts / tx

0.29

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #73,987,367  ·  7 txs across 3 waves  ·  depth 3
parallel ↔ serial

wave w0

wave w1

wave w2

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

0xad2c107f…8d1f

0x065c9d…c394

4 touches
1 conflict

0xf2f76ab3…623e

0x2a68ba…90c5

4 touches
1 conflict

0xdbaa0a45…5389

0x065c9d…c394

3 touches
1 conflict

0xed9f04e5…a2c8

0x065c9d…c394

3 touches
1 conflict

0x06fb9574…6741

0x065c9d…c394

2 touches
0 conflicts

0x0f895050…dc37

0x065c9d…c394

2 touches
0 conflicts

0x10d61a2f…2845

0x065c9d…c394

2 touches
0 conflicts

0x6d34392c…8a19

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 0xad2c107f21…138d1f

← previous block·next block →recent activity