Block #73,438,197

← previous blocknext block →recent activity

Analyzing

Block #73,438,197

18 transactions · 17 stateful · 2026-05-09 10:20:04 UTC

Parallelism

67/100

Blocked

47%

Avg conflicts / tx

1.56

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #73,438,197  ·  18 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

0x00000000…003d

0x065c9d…c394

12 touches
15 conflicts

0x22e295f5…1bef

0x065c9d…c394

10 touches
10 conflicts

0x046a928e…0012

0x2a68ba…90c5

8 touches
6 conflicts

0x4d87512b…897c

0x065c9d…c394

8 touches
6 conflicts

0xf2f76ab3…623e

0x2a68ba…90c5

6 touches
3 conflicts

0x06a96fc5…f659

0x065c9d…c394

4 touches
1 conflict

0x9b36b3e0…1502

0x065c9d…c394

3 touches
1 conflict

0xfd05a633…3ad4

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: 0x065c9d28…a9c394

15 conflicts on slot 0x0000000000…00003d

← previous block·next block →recent activity