← previous blocknext block →recent activity

Analyzing

Block #73,952,894

10 transactions · 7 stateful · 2026-05-11 19:41:45 UTC

Parallelism

80/100

Blocked

43%

Avg conflicts / tx

0.4

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #73,952,894  ·  10 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

0xdf8a66f7…523d

0x065c9d…c394

4 touches
1 conflict

0x7301f2af…c48e

0x2a68ba…90c5

4 touches
1 conflict

0xf2f76ab3…623e

0x2a68ba…90c5

4 touches
1 conflict

0xb21fbb80…ef01

0x065c9d…c394

3 touches
1 conflict

0xbd9bcfe0…0c16

0x065c9d…c394

3 touches
1 conflict

0x143ae8fc…4ab0

0x065c9d…c394

3 touches
1 conflict

0x00000000…0013

0x1b6862…e19c

2 touches
0 conflicts

0x00000000…0015

0x1b6862…e19c

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 0xdf8a66f770…cb523d

← previous block·next block →recent activity