← previous blocknext block →recent activity

Analyzing

Block #73,261,456

28 transactions · 21 stateful · 2026-05-08 14:44:02 UTC

Parallelism

79/100

Blocked

57%

Avg conflicts / tx

1.07

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #73,261,456  ·  28 txs across 6 waves  ·  depth 6
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

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

0xd28bd222…7612

0xd32edf…ff58

11 touches
15 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

10 touches
10 conflicts

0x0b390c61…dc07

0x065c9d…c394

6 touches
3 conflicts

0xbd7e37a9…9eb5

0x065c9d…c394

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0x9c98d98f…75fa

0x065c9d…c394

4 touches
1 conflict

0xbdff944d…447e

0x2a68ba…90c5

4 touches
1 conflict

0x737acb78…fce8

0x34b655…2a6f

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

15 conflicts on slot 0xd28bd22247…b87612

← previous block·next block →recent activity