← previous blocknext block →recent activity

Analyzing

Block #73,681,344

10 transactions · 9 stateful · 2026-05-10 13:22:44 UTC

Parallelism

60/100

Blocked

33%

Avg conflicts / tx

0.6

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #73,681,344  ·  10 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

0x0ac31945…2c72

0x065c9d…c394

6 touches
3 conflicts

0xf2f76ab3…623e

0x2a68ba…90c5

6 touches
3 conflicts

0x0ff6287f…0304

0x065c9d…c394

4 touches
1 conflict

0x98fe643f…6eb9

0x065c9d…c394

3 touches
1 conflict

0x39889e54…ad49

0x065c9d…c394

3 touches
1 conflict

0xf6c98365…be18

0x065c9d…c394

2 touches
0 conflicts

0x09000000…0001

0x000000…1000

2 touches
0 conflicts

0x00000000…0013

0x1b6862…e19c

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: 0x065c9d28…a9c394

3 conflicts on slot 0x0ac3194537…8f2c72

← previous block·next block →recent activity