← previous blocknext block →recent activity

Analyzing

Block #73,652,233

17 transactions · 14 stateful · 2026-05-10 10:06:10 UTC

Parallelism

82/100

Blocked

36%

Avg conflicts / tx

0.35

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #73,652,233  ·  17 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

0x38524fae…9deb

0x34b655…2a6f

6 touches
3 conflicts

0x408e66bb…3d6b

0x34b655…2a6f

4 touches
1 conflict

0x45234a78…e56b

0x34b655…2a6f

4 touches
1 conflict

0x5bad2bef…06ba

0x34b655…2a6f

4 touches
1 conflict

0x64461c10…e86d

0x34b655…2a6f

4 touches
1 conflict

0x97d5efed…1aa4

0x34b655…2a6f

4 touches
1 conflict

0x9c7efe24…3d4b

0x34b655…2a6f

4 touches
1 conflict

0xb0ddfb02…e9e6

0x34b655…2a6f

4 touches
1 conflict

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: 0x34b6552d…112a6f

3 conflicts on slot 0x38524faed4…ae9deb

← previous block·next block →recent activity