← previous blocknext block →recent activity

Analyzing

Block #73,263,231

13 transactions · 12 stateful · 2026-05-08 14:55:51 UTC

Parallelism

46/100

Blocked

67%

Avg conflicts / tx

2

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #73,263,231  ·  13 txs across 7 waves  ·  depth 7
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

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

0x046a928e…0012

0x2a68ba…90c5

10 touches
10 conflicts

0xf2f76ab3…623e

0x2a68ba…90c5

10 touches
10 conflicts

0x00000000…003d

0x065c9d…c394

10 touches
10 conflicts

0xbd7e37a9…9eb5

0x065c9d…c394

4 touches
1 conflict

0x0b390c61…dc07

0x065c9d…c394

4 touches
1 conflict

0x139b5954…10af

0x065c9d…c394

2 touches
0 conflicts

0x40b9d2a8…3304

0x065c9d…c394

2 touches
0 conflicts

0x503ee695…ff73

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

10 conflicts on slot 0x046a928e85…e50012

← previous block·next block →recent activity