← previous blocknext block →recent activity

Analyzing

Block #73,376,993

10 transactions · 10 stateful · 2026-05-09 03:32:47 UTC

Parallelism

70/100

Blocked

20%

Avg conflicts / tx

0.3

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #73,376,993  ·  10 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

0x00000000…003d

0x065c9d…c394

6 touches
3 conflicts

0x4d87512b…897c

0x065c9d…c394

6 touches
3 conflicts

0xf2f76ab3…623e

0x2a68ba…90c5

4 touches
1 conflict

0x19758fea…8d5b

0x065c9d…c394

2 touches
0 conflicts

0x735758e7…e7e2

0x065c9d…c394

2 touches
0 conflicts

0x79bd3c69…38e1

0x065c9d…c394

2 touches
0 conflicts

0xa7fe0d97…ae1c

0x2a68ba…90c5

2 touches
0 conflicts

0x2e2214a9…fe0d

0x8e764f…e322

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 0x0000000000…00003d

← previous block·next block →recent activity