← previous blocknext block →recent activity

Analyzing

Block #73,683,682

12 transactions · 11 stateful · 2026-05-10 13:38:32 UTC

Parallelism

58/100

Blocked

55%

Avg conflicts / tx

1.33

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #73,683,682  ·  12 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

0x00000000…003d

0x065c9d…c394

8 touches
6 conflicts

0x0ac31945…2c72

0x065c9d…c394

6 touches
3 conflicts

0x046a928e…0012

0x2a68ba…90c5

6 touches
3 conflicts

0x529acb6a…fcc6

0x065c9d…c394

4 touches
1 conflict

0x7f87703e…58c8

0x065c9d…c394

2 touches
0 conflicts

0x8e9cb7cc…da4b

0x065c9d…c394

2 touches
0 conflicts

0xcceef543…c64a

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 0xf2f76ab392…f3623e

← previous block·next block →recent activity