← previous blocknext block →recent activity

Analyzing

Block #73,651,155

7 transactions · 7 stateful · 2026-05-10 09:58:56 UTC

Parallelism

43/100

Blocked

43%

Avg conflicts / tx

0.86

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #73,651,155  ·  7 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

0x00000000…003d

0x065c9d…c394

8 touches
6 conflicts

0xb159af88…a9e7

0x065c9d…c394

6 touches
3 conflicts

0x046a928e…0012

0x2a68ba…90c5

4 touches
1 conflict

0x5a855baf…ad04

0x065c9d…c394

3 touches
1 conflict

0x78965d58…9b67

0x065c9d…c394

3 touches
1 conflict

0x194cfc10…c735

0x065c9d…c394

2 touches
0 conflicts

0x6cab82fb…076c

0x065c9d…c394

2 touches
0 conflicts

0x7f81fb82…633e

0x065c9d…c394

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: 0x065c9d28…a9c394

6 conflicts on slot 0x0000000000…00003d

← previous block·next block →recent activity