← previous blocknext block →recent activity

Analyzing

Block #73,748,791

25 transactions · 20 stateful · 2026-05-10 20:57:45 UTC

Parallelism

80/100

Blocked

45%

Avg conflicts / tx

0.6

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #73,748,791  ·  25 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

0x15d039e7…4bb6

0x34b655…2a6f

8 touches
6 conflicts

0x19304b0f…38cb

0xd32edf…ff58

7 touches
6 conflicts

0x00000000…002d

0x1b6862…e19c

6 touches
3 conflicts

0x7322fb4a…635d

0x1b6862…e19c

6 touches
3 conflicts

0xa8e512cf…ba71

0x34b655…2a6f

6 touches
3 conflicts

0xd9f18d9a…141d

0x1b6862…e19c

6 touches
3 conflicts

0x00000000…0012

0x1b6862…e19c

6 touches
3 conflicts

0x00000000…0015

0x1b6862…e19c

6 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: 0x34b6552d…112a6f

6 conflicts on slot 0x15d039e716…294bb6

← previous block·next block →recent activity