← previous blocknext block →recent activity

Analyzing

Block #73,811,348

8 transactions · 8 stateful · 2026-05-11 03:59:11 UTC

Parallelism

75/100

Blocked

25%

Avg conflicts / tx

0.25

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #73,811,348  ·  8 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

0x5d87b441…17ed

0x065c9d…c394

4 touches
1 conflict

0x8fcbbd35…bf07

0x065c9d…c394

4 touches
1 conflict

0x9e2f2afd…27f7

0x065c9d…c394

3 touches
1 conflict

0xe1109852…45b0

0x065c9d…c394

3 touches
1 conflict

0x0c4de2e1…a293

0x065c9d…c394

2 touches
0 conflicts

0x22e295f5…1bef

0x065c9d…c394

2 touches
0 conflicts

0x4d87512b…897c

0x065c9d…c394

2 touches
0 conflicts

0x87614c8e…bbd9

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 0x5d87b441b7…e517ed

← previous block·next block →recent activity