← previous blocknext block →recent activity

Analyzing

Block #73,373,960

12 transactions · 11 stateful · 2026-05-09 03:12:37 UTC

Parallelism

67/100

Blocked

27%

Avg conflicts / tx

0.5

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #73,373,960  ·  12 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

0xa7fe0d97…ae1c

0x2a68ba…90c5

8 touches
6 conflicts

0x385c18ed…57a8

0x065c9d…c394

7 touches
6 conflicts

0xa1087a5c…66c4

0x754704…b603

6 touches
3 conflicts

0x8876d94c…8435

0x2a68ba…90c5

2 touches
0 conflicts

0x12530975…a089

0x3bd359…433a

2 touches
0 conflicts

0x264c6e4e…cbb6

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: 0x2a68ba18…8e90c5

6 conflicts on slot 0xa7fe0d9788…69ae1c

← previous block·next block →recent activity