← previous blocknext block →recent activity

Analyzing

Block #73,594,496

7 transactions · 6 stateful · 2026-05-10 03:39:20 UTC

Parallelism

57/100

Blocked

33%

Avg conflicts / tx

0.57

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #73,594,496  ·  7 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

0xae69c125…2379

0x2a68ba…90c5

6 touches
3 conflicts

0x22e295f5…1bef

0x065c9d…c394

4 touches
1 conflict

0x4d87512b…897c

0x065c9d…c394

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0x88490b24…650f

0xd32edf…ff58

3 touches
1 conflict

0x10761540…aec6

0x065c9d…c394

3 touches
1 conflict

0x72cd8742…cd71

0x065c9d…c394

3 touches
1 conflict

0x7d682807…cdbd

0x065c9d…c394

3 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: 0x2a68ba18…8e90c5

3 conflicts on slot 0xae69c12575…722379

← previous block·next block →recent activity