← previous blocknext block →recent activity

Analyzing

Block #73,964,713

9 transactions · 6 stateful · 2026-05-11 21:00:19 UTC

Parallelism

67/100

Blocked

33%

Avg conflicts / tx

0.33

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #73,964,713  ·  9 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

0xf537eaa0…73c8

0x065c9d…c394

4 touches
1 conflict

0xdfc00c71…3f90

0x065c9d…c394

3 touches
1 conflict

0xed83f68e…5bff

0x065c9d…c394

3 touches
1 conflict

0x60de97fb…8035

0x065c9d…c394

2 touches
0 conflicts

0x6f08361d…bda6

0x065c9d…c394

2 touches
0 conflicts

0x84055a6a…f3da

0x065c9d…c394

2 touches
0 conflicts

0xa91504f9…894f

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

3 conflicts on slot 0x0000000000…00003d

← previous block·next block →recent activity