← previous blocknext block →recent activity

Analyzing

Block #73,991,666

12 transactions · 11 stateful · 2026-05-12 00:01:18 UTC

Parallelism

75/100

Blocked

27%

Avg conflicts / tx

0.25

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #73,991,666  ·  12 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

4 touches
1 conflict

0x2b88e1be…8d11

0x065c9d…c394

4 touches
1 conflict

0xd9f18d9a…141d

0x1b6862…e19c

4 touches
1 conflict

0x310a7246…2dcb

0x34b655…2a6f

4 touches
1 conflict

0x763e165a…e979

0x34b655…2a6f

4 touches
1 conflict

0xb6ed511f…6b68

0x34b655…2a6f

4 touches
1 conflict

0xf00e711b…c539

0x34b655…2a6f

4 touches
1 conflict

0x6ef8fc0d…e533

0x065c9d…c394

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

1 conflict on slot 0x0000000000…00003d

← previous block·next block →recent activity