← previous blocknext block →recent activity

Analyzing

Block #73,751,582

13 transactions · 12 stateful · 2026-05-10 21:16:36 UTC

Parallelism

77/100

Blocked

42%

Avg conflicts / tx

0.69

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #73,751,582  ·  13 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

0x8a2657f5…e008

0x34b655…2a6f

6 touches
3 conflicts

0x4d87512b…897c

0x065c9d…c394

6 touches
3 conflicts

0x7f161035…cb82

0x0594c7…a3be

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0x8876d94c…8435

0x2a68ba…90c5

4 touches
1 conflict

0xf2f76ab3…623e

0x2a68ba…90c5

4 touches
1 conflict

0x0eac6378…36f4

0x34b655…2a6f

4 touches
1 conflict

0x2189fe5f…d43e

0x34b655…2a6f

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: 0x34b6552d…112a6f

3 conflicts on slot 0x8a2657f5c3…4ce008

← previous block·next block →recent activity