← previous blocknext block →recent activity

Analyzing

Block #73,963,796

21 transactions · 17 stateful · 2026-05-11 20:54:15 UTC

Parallelism

81/100

Blocked

29%

Avg conflicts / tx

0.43

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #73,963,796  ·  21 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

0xcb45d9d6…cb82

0x1b6862…e19c

8 touches
6 conflicts

0x00000000…001a

0x1b6862…e19c

8 touches
6 conflicts

0x217670f5…100a

0xd32edf…ff58

7 touches
6 conflicts

0xd9f18d9a…141d

0x1b6862…e19c

6 touches
3 conflicts

0x00000000…0012

0x1b6862…e19c

6 touches
3 conflicts

0xf6cc7de8…0b4a

0x3bd359…433a

4 touches
1 conflict

0xd98b3c10…67b8

0x34b655…2a6f

4 touches
1 conflict

0x00000000…0000

0x63e48b…53f2

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 0xcb45d9d62a…b1cb82

← previous block·next block →recent activity