← previous blocknext block →recent activity

Analyzing

Block #73,270,609

18 transactions · 17 stateful · 2026-05-08 15:45:01 UTC

Parallelism

78/100

Blocked

35%

Avg conflicts / tx

0.61

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #73,270,609  ·  18 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

0xbd7e37a9…9eb5

0x065c9d…c394

8 touches
6 conflicts

0x0b390c61…dc07

0x065c9d…c394

6 touches
3 conflicts

0xfff38d9f…7063

0x8d66a4…3095

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0x8a35acfb…d1a9

0x8d66a4…3095

4 touches
1 conflict

0x8a35acfb…d1ab

0x8d66a4…3095

4 touches
1 conflict

0x8a35acfb…d1ad

0x8d66a4…3095

4 touches
1 conflict

0x8a35acfb…d1ae

0x8d66a4…3095

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 0xbd7e37a9b5…859eb5

← previous block·next block →recent activity