← previous blocknext block →recent activity

Analyzing

Block #73,639,258

14 transactions · 11 stateful · 2026-05-10 08:38:52 UTC

Parallelism

86/100

Blocked

27%

Avg conflicts / tx

0.21

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #73,639,258  ·  14 txs across 2 waves  ·  depth 2
parallel ↔ serial

wave w0

wave w1

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

0xc9e97522…3519

0x2a68ba…90c5

4 touches
1 conflict

0xea02471d…1539

0x34b655…2a6f

4 touches
1 conflict

0xa1087a5c…66c4

0x754704…b603

4 touches
1 conflict

0x3fc782ae…a3b5

0x065c9d…c394

4 touches
1 conflict

0x0a8dce7b…41f6

0xd32edf…ff58

3 touches
1 conflict

0x00000000…0005

0x0594c7…a3be

2 touches
0 conflicts

0x325f339c…ccbe

0x0594c7…a3be

2 touches
0 conflicts

0x00f7e3b7…e015

0x188d58…ea8e

2 touches
0 conflicts

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: 0x2a68ba18…8e90c5

1 conflict on slot 0xc9e9752290…9c3519

← previous block·next block →recent activity