← previous blocknext block →recent activity

Analyzing

Block #73,921,100

19 transactions · 17 stateful · 2026-05-11 16:10:16 UTC

Parallelism

74/100

Blocked

59%

Avg conflicts / tx

0.79

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #73,921,100  ·  19 txs across 5 waves  ·  depth 5
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

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

6 touches
3 conflicts

0x046a928e…0012

0x2a68ba…90c5

6 touches
3 conflicts

0x00000000…0019

0x1b6862…e19c

6 touches
3 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0xcb45d9d6…cb81

0x1b6862…e19c

6 touches
3 conflicts

0x61ae8367…72f0

0xd32edf…ff58

5 touches
3 conflicts

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0x8c99bc23…f309

0x34b655…2a6f

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

3 conflicts on slot 0x6f08361da9…89bda6

← previous block·next block →recent activity