← previous blocknext block →recent activity

Analyzing

Block #73,917,731

13 transactions · 12 stateful · 2026-05-11 15:47:50 UTC

Parallelism

54/100

Blocked

58%

Avg conflicts / tx

1.23

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #73,917,731  ·  13 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

0xf537eaa0…73c8

0x065c9d…c394

10 touches
10 conflicts

0xd9f18d9a…141d

0x1b6862…e19c

6 touches
3 conflicts

0xcb45d9d6…cb81

0x1b6862…e19c

6 touches
3 conflicts

0x00000000…003d

0x065c9d…c394

6 touches
3 conflicts

0x00000000…0019

0x1b6862…e19c

6 touches
3 conflicts

0x00000000…0012

0x1b6862…e19c

6 touches
3 conflicts

0x6f08361d…bda6

0x065c9d…c394

6 touches
3 conflicts

0x9600c42e…f710

0xd32edf…ff58

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

10 conflicts on slot 0xf537eaa0c6…3873c8

← previous block·next block →recent activity