← previous blocknext block →recent activity

Analyzing

Block #73,681,386

14 transactions · 14 stateful · 2026-05-10 13:23:01 UTC

Parallelism

64/100

Blocked

50%

Avg conflicts / tx

1.14

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #73,681,386  ·  14 txs across 5 waves  ·  depth 5
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

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

0xf2f76ab3…623e

0x2a68ba…90c5

10 touches
10 conflicts

0x529acb6a…fcc6

0x065c9d…c394

6 touches
3 conflicts

0xac33ff75…077b

0xfa32f9…f3f0

4 touches
1 conflict

0x0ac31945…2c72

0x065c9d…c394

4 touches
1 conflict

0x8a35acfb…d1ab

0x8d66a4…3095

4 touches
1 conflict

0xe89e1a22…ce49

0x8d66a4…3095

4 touches
1 conflict

0x00000000…0000

0xfa32f9…f3f0

4 touches
1 conflict

0x00000000…0001

0xfa32f9…f3f0

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

10 conflicts on slot 0xf2f76ab392…f3623e

← previous block·next block →recent activity