← previous blocknext block →recent activity

Analyzing

Block #73,661,362

11 transactions · 10 stateful · 2026-05-10 11:07:41 UTC

Parallelism

73/100

Blocked

20%

Avg conflicts / tx

0.36

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #73,661,362  ·  11 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

0x5d96e332…ee37

0x065c9d…c394

6 touches
3 conflicts

0xc9e97522…3519

0x2a68ba…90c5

6 touches
3 conflicts

0xa1087a5c…66c4

0x754704…b603

4 touches
1 conflict

0xd80d8e7c…938a

0xd32edf…ff58

3 touches
1 conflict

0x00000000…0001

0x010592…1c83

2 touches
0 conflicts

0x78ae17f2…53be

0x000000…012a

2 touches
0 conflicts

0x335a161d…fe7f

0x000000…012a

2 touches
0 conflicts

0x264c6e4e…cbb6

0x3bd359…433a

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 0x5d96e332f6…fbee37

← previous block·next block →recent activity