← previous blocknext block →recent activity

Analyzing

Block #73,610,832

17 transactions · 9 stateful · 2026-05-10 05:28:00 UTC

Parallelism

82/100

Blocked

33%

Avg conflicts / tx

0.24

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #73,610,832  ·  17 txs across 3 waves  ·  depth 3
parallel ↔ serial

wave w0

wave w1

wave w2

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

0x8240d70c…7c3b

0x34b655…2a6f

6 touches
3 conflicts

0x85a88798…f85e

0x34b655…2a6f

4 touches
1 conflict

0x8c99bc23…f309

0x34b655…2a6f

4 touches
1 conflict

0xfa2527aa…9dd5

0x34b655…2a6f

4 touches
1 conflict

0x0d622e34…0000

0x681e90…ae09

4 touches
1 conflict

0x3e90b8f3…d80f

0x065c9d…c394

2 touches
0 conflicts

0x4fcb0db8…2b93

0x065c9d…c394

2 touches
0 conflicts

0xf9f964c0…9e65

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: 0x34b6552d…112a6f

3 conflicts on slot 0x8240d70c8a…f27c3b

← previous block·next block →recent activity