← previous blocknext block →recent activity

Analyzing

Block #73,861,127

17 transactions · 15 stateful · 2026-05-11 09:30:40 UTC

Parallelism

65/100

Blocked

33%

Avg conflicts / tx

0.94

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #73,861,127  ·  17 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

0xa39b3b0b…3a33

0xd32edf…ff58

11 touches
15 conflicts

0xcb45d9d6…cb80

0x1b6862…e19c

8 touches
6 conflicts

0xd9f18d9a…141d

0x1b6862…e19c

8 touches
6 conflicts

0x00000000…0018

0x1b6862…e19c

8 touches
6 conflicts

0x00000000…0012

0x1b6862…e19c

8 touches
6 conflicts

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0x22e295f5…1bef

0x065c9d…c394

4 touches
1 conflict

0x4d87512b…897c

0x065c9d…c394

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: 0xd32edf66…9fff58

15 conflicts on slot 0xa39b3b0b9a…c03a33

← previous block·next block →recent activity