← previous blocknext block →recent activity

Analyzing

Block #73,334,603

14 transactions · 12 stateful · 2026-05-08 22:50:47 UTC

Parallelism

86/100

Blocked

17%

Avg conflicts / tx

0.14

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #73,334,603  ·  14 txs across 2 waves  ·  depth 2
parallel ↔ serial

wave w0

wave w1

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…003d

0x065c9d…c394

4 touches
1 conflict

0xa15427f6…d932

0x34b655…2a6f

4 touches
1 conflict

0x0b000000…0002

0x000000…1000

2 touches
0 conflicts

0x090c91db…baa0

0x065c9d…c394

2 touches
0 conflicts

0x68fc1694…16b6

0x065c9d…c394

2 touches
0 conflicts

0x79c10a66…2099

0x065c9d…c394

2 touches
0 conflicts

0x7e2909bc…1257

0x065c9d…c394

2 touches
0 conflicts

0x92838aed…8d61

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: 0x065c9d28…a9c394

1 conflict on slot 0x0000000000…00003d

← previous block·next block →recent activity