← previous blocknext block →recent activity

Analyzing

Block #73,381,821

30 transactions · 23 stateful · 2026-05-09 04:04:52 UTC

Parallelism

87/100

Blocked

30%

Avg conflicts / tx

0.53

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #73,381,821  ·  30 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

0x00000000…003d

0x065c9d…c394

8 touches
6 conflicts

0x8a2657f5…e008

0x34b655…2a6f

6 touches
3 conflicts

0xc9d7a8db…e395

0xd32edf…ff58

5 touches
3 conflicts

0x22e295f5…1bef

0x065c9d…c394

4 touches
1 conflict

0x4d87512b…897c

0x065c9d…c394

4 touches
1 conflict

0x00000000…0004

0xd5b70d…615b

4 touches
1 conflict

0x12309510…0ac2

0x000000…012a

4 touches
1 conflict

0x18aed20c…48f3

0x000000…012a

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

← previous block·next block →recent activity