← previous blocknext block →recent activity

Analyzing

Block #73,427,274

13 transactions · 12 stateful · 2026-05-09 09:07:32 UTC

Parallelism

69/100

Blocked

42%

Avg conflicts / tx

0.62

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #73,427,274  ·  13 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

0x6f08361d…bda6

0x065c9d…c394

8 touches
6 conflicts

0xf2f76ab3…623e

0x2a68ba…90c5

6 touches
3 conflicts

0x1bc9b1ca…85ef

0x34b655…2a6f

4 touches
1 conflict

0x9ea57326…329f

0x34b655…2a6f

4 touches
1 conflict

0xac2a0273…721b

0x34b655…2a6f

4 touches
1 conflict

0xb337c4d8…f9d3

0x34b655…2a6f

4 touches
1 conflict

0xb6be69cd…f3a6

0x34b655…2a6f

4 touches
1 conflict

0xf4df8b4f…e396

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

6 conflicts on slot 0x6f08361da9…89bda6

← previous block·next block →recent activity