← previous blocknext block →recent activity

Analyzing

Block #73,693,739

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

Parallelism

74/100

Blocked

44%

Avg conflicts / tx

0.52

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #73,693,739  ·  23 txs across 6 waves  ·  depth 6
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

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

8 touches
6 conflicts

0x67c9847d…6169

0xd32edf…ff58

5 touches
3 conflicts

0x838d1c6b…3b57

0x065c9d…c394

5 touches
3 conflicts

0x0175b7a6…1dbb

0x6c4bfa…a540

4 touches
1 conflict

0x846f2172…fd54

0x0555e3…2b9c

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0x0175b7a6…1dbd

0x6c4bfa…a540

4 touches
1 conflict

0x0ef1e663…8f2a

0x6c4bfa…a540

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

6 conflicts on slot 0xae69c12575…722379

← previous block·next block →recent activity