← previous blocknext block →recent activity

Analyzing

Block #73,673,693

13 transactions · 11 stateful · 2026-05-10 12:30:59 UTC

Parallelism

69/100

Blocked

27%

Avg conflicts / tx

0.31

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #73,673,693  ·  13 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

0x336c8edd…10a7

0x065c9d…c394

6 touches
3 conflicts

0xa1087a5c…66c4

0x754704…b603

6 touches
3 conflicts

0xc3c8642a…7da5

0x2a68ba…90c5

6 touches
3 conflicts

0x17606ba6…1b6e

0x754704…b603

4 touches
1 conflict

0x264c6e4e…cbb6

0x3bd359…433a

2 touches
0 conflicts

0x74fe76c9…225f

0x3bd359…433a

2 touches
0 conflicts

0xa980598e…ec52

0x3bd359…433a

2 touches
0 conflicts

0x00000000…0001

0x453805…c7fd

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

3 conflicts on slot 0x336c8edd35…7d10a7

← previous block·next block →recent activity