← previous blocknext block →recent activity

Analyzing

Block #73,679,557

33 transactions · 24 stateful · 2026-05-10 13:10:40 UTC

Parallelism

73/100

Blocked

42%

Avg conflicts / tx

0.88

Longest chain

9 deep

Execution timeline

did this block parallelize well?

view

block #73,679,557  ·  33 txs across 9 waves  ·  depth 9
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

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

0xe89b64b8…89ef

0xd32edf…ff58

11 touches
15 conflicts

0x529acb6a…fcc6

0x065c9d…c394

8 touches
6 conflicts

0x046a928e…0012

0x2a68ba…90c5

8 touches
6 conflicts

0x00000000…003d

0x065c9d…c394

8 touches
6 conflicts

0x393d6714…db85

0x065c9d…c394

3 touches
1 conflict

0x657539be…fd8d

0x065c9d…c394

3 touches
1 conflict

0x00000000…0004

0x5afd3e…7620

2 touches
0 conflicts

0x00000000…0005

0x5afd3e…7620

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

15 conflicts on slot 0xe89b64b8d3…f589ef

← previous block·next block →recent activity