← previous blocknext block →recent activity

Analyzing

Block #73,921,764

12 transactions · 12 stateful · 2026-05-11 16:14:41 UTC

Parallelism

67/100

Blocked

33%

Avg conflicts / tx

0.75

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #73,921,764  ·  12 txs across 4 waves  ·  depth 4
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

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…0012

0x1b6862…e19c

8 touches
6 conflicts

0xd9f18d9a…141d

0x1b6862…e19c

8 touches
6 conflicts

0xcb45d9d6…cb81

0x1b6862…e19c

8 touches
6 conflicts

0x00000000…0019

0x1b6862…e19c

8 touches
6 conflicts

0xd3183954…b7de

0xd32edf…ff58

7 touches
6 conflicts

0x00000000…003d

0x065c9d…c394

6 touches
3 conflicts

0x22e295f5…1bef

0x065c9d…c394

6 touches
3 conflicts

0x4d1acd7c…f345

0x5e1b1a…7777

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: 0x1b68626d…2de19c

6 conflicts on slot 0x0000000000…000012

← previous block·next block →recent activity