← previous blocknext block →recent activity

Analyzing

Block #73,386,936

15 transactions · 13 stateful · 2026-05-09 04:38:55 UTC

Parallelism

67/100

Blocked

38%

Avg conflicts / tx

0.47

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #73,386,936  ·  15 txs across 5 waves  ·  depth 5
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

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

0x174dca62…9c57

0xd32edf…ff58

5 touches
3 conflicts

0x8a2657f5…e008

0x34b655…2a6f

4 touches
1 conflict

0x22e295f5…1bef

0x065c9d…c394

4 touches
1 conflict

0xcb45d9d6…cb86

0x1b6862…e19c

4 touches
1 conflict

0x00000000…001e

0x1b6862…e19c

4 touches
1 conflict

0x24e0a6b3…4d27

0x065c9d…c394

4 touches
1 conflict

0x046a928e…0012

0x2a68ba…90c5

4 touches
1 conflict

0xc0ad2e16…8866

0x065c9d…c394

3 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: 0xd32edf66…9fff58

3 conflicts on slot 0x174dca6249…769c57

← previous block·next block →recent activity