← previous blocknext block →recent activity

Analyzing

Block #73,034,838

26 transactions · 22 stateful · 2026-05-07 13:36:24 UTC

Parallelism

85/100

Blocked

41%

Avg conflicts / tx

0.58

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #73,034,838  ·  26 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

0x00000000…0002

0xd574ca…7ab1

8 touches
6 conflicts

0x8a35acfb…d1ac

0x8d66a4…3095

6 touches
3 conflicts

0x60f7fbaf…bd58

0x34b655…2a6f

6 touches
3 conflicts

0x17606ba6…1b6e

0x754704…b603

6 touches
3 conflicts

0xfff38d9f…7063

0x8d66a4…3095

4 touches
1 conflict

0x3df3de0d…cd8b

0x34b655…2a6f

4 touches
1 conflict

0xd98b3c10…67b8

0x34b655…2a6f

4 touches
1 conflict

0x01e7b865…6e6d

0x188d58…ea8e

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: 0xd574cae5…037ab1

6 conflicts on slot 0x0000000000…000002

← previous block·next block →recent activity