← previous blocknext block →recent activity

Analyzing

Block #73,383,964

12 transactions · 9 stateful · 2026-05-09 04:19:08 UTC

Parallelism

58/100

Blocked

44%

Avg conflicts / tx

0.83

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #73,383,964  ·  12 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

0x046a928e…0012

0x2a68ba…90c5

10 touches
10 conflicts

0xb159af88…a9e7

0x065c9d…c394

6 touches
3 conflicts

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0x92339d95…0800

0x0000a8…8888

2 touches
0 conflicts

0x4d87512b…897c

0x065c9d…c394

2 touches
0 conflicts

0x584ad8f7…ccac

0x065c9d…c394

2 touches
0 conflicts

0xaab85040…0bcc

0x065c9d…c394

2 touches
0 conflicts

0xe3770d94…4c22

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: 0x2a68ba18…8e90c5

10 conflicts on slot 0x046a928e85…e50012

← previous block·next block →recent activity