← previous blocknext block →recent activity

Analyzing

Block #73,263,483

10 transactions · 10 stateful · 2026-05-08 14:57:32 UTC

Parallelism

70/100

Blocked

30%

Avg conflicts / tx

0.4

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #73,263,483  ·  10 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

0x0b390c61…dc07

0x065c9d…c394

6 touches
3 conflicts

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0xdbc578df…706a

0x34b655…2a6f

4 touches
1 conflict

0xe6bc2705…d15b

0x34b655…2a6f

4 touches
1 conflict

0x3a874624…492c

0x065c9d…c394

2 touches
0 conflicts

0xb514e6a9…8f15

0x065c9d…c394

2 touches
0 conflicts

0xbd7e37a9…9eb5

0x065c9d…c394

2 touches
0 conflicts

0xf72c7b20…28f3

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

3 conflicts on slot 0x0b390c6160…02dc07

← previous block·next block →recent activity