← previous blocknext block →recent activity

Analyzing

Block #73,263,259

18 transactions · 12 stateful · 2026-05-08 14:56:02 UTC

Parallelism

78/100

Blocked

33%

Avg conflicts / tx

0.39

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #73,263,259  ·  18 txs across 4 waves  ·  depth 4
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

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…0002

0xab3526…fa38

8 touches
6 conflicts

0xf2f76ab3…623e

0x2a68ba…90c5

4 touches
1 conflict

0x0b390c61…dc07

0x065c9d…c394

4 touches
1 conflict

0x503ee695…ff73

0x065c9d…c394

3 touches
1 conflict

0x33a0b561…ad27

0x065c9d…c394

2 touches
0 conflicts

0x5e8c8272…b472

0x065c9d…c394

2 touches
0 conflicts

0x8e43a6e9…fba4

0x065c9d…c394

2 touches
0 conflicts

0xbd7e37a9…9eb5

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: 0xab35264b…1cfa38

6 conflicts on slot 0x0000000000…000002

← previous block·next block →recent activity