← previous blocknext block →recent activity

Analyzing

Block #73,034,879

16 transactions · 9 stateful · 2026-05-07 13:36:40 UTC

Parallelism

75/100

Blocked

44%

Avg conflicts / tx

0.44

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #73,034,879  ·  16 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

0xd98b3c10…67b8

0x34b655…2a6f

8 touches
6 conflicts

0x109d8a52…a7b7

0x34b655…2a6f

6 touches
3 conflicts

0xfe20cb8f…f03d

0x34b655…2a6f

4 touches
1 conflict

0x00000000…0002

0xd574ca…7ab1

4 touches
1 conflict

0x32aa281b…0f8e

0x34b655…2a6f

4 touches
1 conflict

0x388e001a…7e04

0x34b655…2a6f

4 touches
1 conflict

0x759dccc6…a766

0x34b655…2a6f

4 touches
1 conflict

0x7b97d40a…09ed

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: 0x34b6552d…112a6f

6 conflicts on slot 0xd98b3c102b…ca67b8

← previous block·next block →recent activity