← previous blocknext block →recent activity

Analyzing

Block #73,211,942

10 transactions · 10 stateful · 2026-05-08 09:14:46 UTC

Parallelism

70/100

Blocked

20%

Avg conflicts / tx

0.4

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #73,211,942  ·  10 txs across 3 waves  ·  depth 3
parallel ↔ serial

wave w0

wave w1

wave w2

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

0x00000000…003d

0x065c9d…c394

6 touches
3 conflicts

0x4e5ebbf7…ae70

0xc8689a…ee79

4 touches
1 conflict

0x00000000…0012

0x1b6862…e19c

4 touches
1 conflict

0x70b2f813…783c

0x2a68ba…90c5

4 touches
1 conflict

0x00000000…000b

0x6ca43f…c331

4 touches
1 conflict

0x554f1ada…6916

0x6ca43f…c331

4 touches
1 conflict

0xfca16cf3…8ea9

0x065c9d…c394

3 touches
1 conflict

0x6c0cecce…60fc

0x065c9d…c394

2 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

3 conflicts on slot 0x0000000000…00003d

← previous block·next block →recent activity