← previous blocknext block →recent activity

Analyzing

Block #74,353,166

19 transactions · 17 stateful · 2026-05-13 16:06:53 UTC

Parallelism

68/100

Blocked

59%

Avg conflicts / tx

1.11

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #74,353,166  ·  19 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

0x56d5c352…5e08

0xd32edf…ff58

9 touches
10 conflicts

0xa472d565…9fe4

0x3bd359…433a

8 touches
6 conflicts

0x30276c1c…47b4

0x2a68ba…90c5

6 touches
3 conflicts

0x41755291…977f

0x065c9d…c394

6 touches
3 conflicts

0x6c5f1ba2…bb2c

0x065c9d…c394

5 touches
3 conflicts

0x00000000…0029

0x1b6862…e19c

4 touches
1 conflict

0xba5743c7…21c0

0x1b6862…e19c

4 touches
1 conflict

0xd9f18d9a…141d

0x1b6862…e19c

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

10 conflicts on slot 0x56d5c3526a…275e08

← previous block·next block →recent activity