← previous blocknext block →recent activity

Analyzing

Block #73,706,372

23 transactions · 14 stateful · 2026-05-10 16:11:26 UTC

Parallelism

87/100

Blocked

29%

Avg conflicts / tx

0.22

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #73,706,372  ·  23 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

0xfa5660c3…cab2

0xd32edf…ff58

5 touches
3 conflicts

0x33018431…8f5d

0x188d58…ea8e

4 touches
1 conflict

0x4aeddb00…aa58

0x065c9d…c394

4 touches
1 conflict

0x33018431…8f5c

0x188d58…ea8e

4 touches
1 conflict

0x17606ba6…1b6e

0x754704…b603

4 touches
1 conflict

0x335a161d…fe7f

0x000000…012a

2 touches
0 conflicts

0x0d622e34…0000

0x681e90…ae09

2 touches
0 conflicts

0x2f77f0f6…4a92

0x188d58…ea8e

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

3 conflicts on slot 0xfa5660c35a…e7cab2

← previous block·next block →recent activity