← previous blocknext block →recent activity

Analyzing

Block #73,201,857

33 transactions · 27 stateful · 2026-05-08 08:07:44 UTC

Parallelism

76/100

Blocked

59%

Avg conflicts / tx

1.15

Longest chain

8 deep

Execution timeline

did this block parallelize well?

view

block #73,201,857  ·  33 txs across 8 waves  ·  depth 8
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

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

0x04b73644…1151

0xd32edf…ff58

11 touches
15 conflicts

0xc3c8642a…7da5

0x2a68ba…90c5

10 touches
10 conflicts

0x97c6f2a8…81c3

0x065c9d…c394

9 touches
10 conflicts

0x0d622e34…0000

0x681e90…ae09

8 touches
6 conflicts

0x00000000…003d

0x065c9d…c394

6 touches
3 conflicts

0x7f189cf6…afab

0x065c9d…c394

6 touches
3 conflicts

0x00000000…0013

0x1b6862…e19c

6 touches
3 conflicts

0x00000000…0015

0x1b6862…e19c

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

15 conflicts on slot 0x04b7364415…c71151

← previous block·next block →recent activity