← previous blocknext block →recent activity

Analyzing

Block #73,391,203

23 transactions · 18 stateful · 2026-05-09 05:07:18 UTC

Parallelism

74/100

Blocked

39%

Avg conflicts / tx

0.78

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #73,391,203  ·  23 txs across 6 waves  ·  depth 6
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

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

0x6f936f92…19b6

0xd32edf…ff58

11 touches
15 conflicts

0x22e295f5…1bef

0x065c9d…c394

6 touches
3 conflicts

0xe038916c…b1be

0x2a68ba…90c5

6 touches
3 conflicts

0xac7ff9bb…139d

0x065c9d…c394

4 touches
1 conflict

0x00000000…0012

0x1b6862…e19c

4 touches
1 conflict

0x00000000…0013

0x1b6862…e19c

4 touches
1 conflict

0x00000000…0015

0x1b6862…e19c

4 touches
1 conflict

0x00000000…001e

0x1b6862…e19c

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

15 conflicts on slot 0x6f936f92b8…8e19b6

← previous block·next block →recent activity