← previous blocknext block →recent activity

Analyzing

Block #73,816,980

8 transactions · 7 stateful · 2026-05-11 04:36:36 UTC

Parallelism

50/100

Blocked

43%

Avg conflicts / tx

0.75

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #73,816,980  ·  8 txs across 4 waves  ·  depth 4
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

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

8 touches
6 conflicts

0x00000000…003d

0x065c9d…c394

6 touches
3 conflicts

0xed57bddf…1abf

0xc8689a…ee79

4 touches
1 conflict

0xc9e97522…3519

0x2a68ba…90c5

4 touches
1 conflict

0x1a4b4152…0a08

0x6c4bfa…a540

4 touches
1 conflict

0x2e2214a9…fe0d

0x6c4bfa…a540

4 touches
1 conflict

0x3e4b8d9f…b8a7

0x6c4bfa…a540

4 touches
1 conflict

0x50997ada…364d

0x6c4bfa…a540

4 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: 0x065c9d28…a9c394

6 conflicts on slot 0x22e295f5d8…ac1bef

← previous block·next block →recent activity