← previous blocknext block →recent activity

Analyzing

Block #73,041,761

19 transactions · 15 stateful · 2026-05-07 14:22:27 UTC

Parallelism

63/100

Blocked

53%

Avg conflicts / tx

1.42

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #73,041,761  ·  19 txs across 7 waves  ·  depth 7
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

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

0xe54e6ca8…dfa1

0xd32edf…ff58

13 touches
21 conflicts

0x70b2f813…783c

0x2a68ba…90c5

8 touches
6 conflicts

0xa1087a5c…66c4

0x754704…b603

8 touches
6 conflicts

0xf33aefd3…cb07

0x065c9d…c394

6 touches
3 conflicts

0x09beabbc…065e

0x188d58…ea8e

4 touches
1 conflict

0x09beabbc…065c

0x188d58…ea8e

4 touches
1 conflict

0x09000000…0001

0x000000…1000

2 touches
0 conflicts

0x00000000…0003

0x5e60bc…fe22

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

21 conflicts on slot 0xe54e6ca814…c4dfa1

← previous block·next block →recent activity