← previous blocknext block →recent activity

Analyzing

Block #73,921,666

11 transactions · 8 stateful · 2026-05-11 16:14:01 UTC

Parallelism

55/100

Blocked

63%

Avg conflicts / tx

0.73

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #73,921,666  ·  11 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

0x046a928e…0012

0x2a68ba…90c5

6 touches
3 conflicts

0xe20db839…7577

0x065c9d…c394

4 touches
1 conflict

0x6f08361d…bda6

0x065c9d…c394

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0x965d5b8a…b9f2

0x065c9d…c394

4 touches
1 conflict

0xc77f6b4b…27ac

0x065c9d…c394

4 touches
1 conflict

0x9b42b9c9…fca8

0x065c9d…c394

3 touches
1 conflict

0x057d66f1…d833

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: 0x2a68ba18…8e90c5

3 conflicts on slot 0x046a928e85…e50012

← previous block·next block →recent activity