← previous blocknext block →recent activity

Analyzing

Block #73,913,286

36 transactions · 23 stateful · 2026-05-11 15:18:07 UTC

Parallelism

81/100

Blocked

48%

Avg conflicts / tx

0.78

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #73,913,286  ·  36 txs across 7 waves  ·  depth 7
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

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

0x6f08361d…bda6

0x065c9d…c394

10 touches
10 conflicts

0xf537eaa0…73c8

0x065c9d…c394

10 touches
10 conflicts

0x00000000…003d

0x065c9d…c394

6 touches
3 conflicts

0x765c236f…ff45

0x2a68ba…90c5

6 touches
3 conflicts

0x046a928e…0012

0x2a68ba…90c5

6 touches
3 conflicts

0x16232a40…bad7

0xd32edf…ff58

5 touches
3 conflicts

0x23939742…6af7

0x065c9d…c394

5 touches
3 conflicts

0xf6cc7de8…0b4a

0x3bd359…433a

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

10 conflicts on slot 0x6f08361da9…89bda6

← previous block·next block →recent activity