← previous blocknext block →recent activity

Analyzing

Block #73,523,377

38 transactions · 28 stateful · 2026-05-09 19:46:52 UTC

Parallelism

68/100

Blocked

64%

Avg conflicts / tx

1.45

Longest chain

12 deep

Execution timeline

did this block parallelize well?

view

block #73,523,377  ·  38 txs across 12 waves  ·  depth 12
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

wave w9

wave w10

wave w11

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

0x8f86b4bd…b765

0xd32edf…ff58

15 touches
28 conflicts

0x00000000…003d

0x065c9d…c394

12 touches
15 conflicts

0x4d87512b…897c

0x065c9d…c394

6 touches
3 conflicts

0x046a928e…0012

0x2a68ba…90c5

6 touches
3 conflicts

0xf2f76ab3…623e

0x2a68ba…90c5

6 touches
3 conflicts

0xa1087a5c…66c4

0x754704…b603

6 touches
3 conflicts

0x22e295f5…1bef

0x065c9d…c394

6 touches
3 conflicts

0x00000000…0029

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

28 conflicts on slot 0x8f86b4bdb9…e6b765

← previous block·next block →recent activity