← previous blocknext block →recent activity

Analyzing

Block #73,922,859

24 transactions · 16 stateful · 2026-05-11 16:21:58 UTC

Parallelism

79/100

Blocked

50%

Avg conflicts / tx

0.71

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #73,922,859  ·  24 txs across 5 waves  ·  depth 5
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

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

0x8155872d…2642

0xd32edf…ff58

9 touches
10 conflicts

0x6f08361d…bda6

0x065c9d…c394

6 touches
3 conflicts

0xf2f76ab3…623e

0x2a68ba…90c5

6 touches
3 conflicts

0x75f3d8c5…9efc

0x065c9d…c394

4 touches
1 conflict

0x5bfd2e59…4fde

0x065c9d…c394

4 touches
1 conflict

0x79084bee…e1d2

0x065c9d…c394

3 touches
1 conflict

0xceadc67c…e0b4

0x065c9d…c394

3 touches
1 conflict

0x0704156b…22c7

0x065c9d…c394

3 touches
1 conflict

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: 0xd32edf66…9fff58

10 conflicts on slot 0x8155872d50…e12642

← previous block·next block →recent activity