← previous blocknext block →recent activity

Analyzing

Block #73,660,455

18 transactions · 13 stateful · 2026-05-10 11:01:34 UTC

Parallelism

78/100

Blocked

31%

Avg conflicts / tx

0.39

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #73,660,455  ·  18 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

0x8d40dd61…2c45

0xd32edf…ff58

7 touches
6 conflicts

0xc9e97522…3519

0x2a68ba…90c5

4 touches
1 conflict

0xb27c9cbe…7944

0xa6afd3…d132

4 touches
1 conflict

0x11b69a7e…334e

0xee8c0e…1242

4 touches
1 conflict

0x0df06d44…4f2b

0x065c9d…c394

4 touches
1 conflict

0x8876d94c…8435

0x2a68ba…90c5

4 touches
1 conflict

0xa1087a5c…66c4

0x754704…b603

2 touches
0 conflicts

0xda359e52…bbc0

0x754704…b603

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: 0xd32edf66…9fff58

6 conflicts on slot 0x8d40dd61e5…342c45

← previous block·next block →recent activity