← previous blocknext block →recent activity

Analyzing

Block #73,308,309

12 transactions · 11 stateful · 2026-05-08 19:55:51 UTC

Parallelism

75/100

Blocked

36%

Avg conflicts / tx

0.42

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #73,308,309  ·  12 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

0x00000000…0002

0xab3526…fa38

6 touches
3 conflicts

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0x2d1d58f7…0b68

0xd32edf…ff58

3 touches
1 conflict

0x0de35b13…0bdd

0x065c9d…c394

2 touches
0 conflicts

0x15b463fd…bad0

0x065c9d…c394

2 touches
0 conflicts

0xa09a01b3…dcea

0x065c9d…c394

2 touches
0 conflicts

0xa5cd14eb…8ff5

0x065c9d…c394

2 touches
0 conflicts

0xafc0f724…1cb2

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: 0xab35264b…1cfa38

3 conflicts on slot 0x0000000000…000002

← previous block·next block →recent activity