← previous blocknext block →recent activity

Analyzing

Block #74,565,972

42 transactions · 26 stateful · 2026-05-14 15:49:05 UTC

Parallelism

76/100

Blocked

42%

Avg conflicts / tx

1.12

Longest chain

10 deep

Execution timeline

did this block parallelize well?

view

block #74,565,972  ·  42 txs across 10 waves  ·  depth 10
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

wave w9

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

0xfdc0fc0b…2b6d

0xd32edf…ff58

19 touches
45 conflicts

0x37699b20…1075

0x1b6862…e19c

4 touches
1 conflict

0x00000000…0015

0x1b6862…e19c

4 touches
1 conflict

0x8e8bad91…4e4b

0x1b6862…e19c

4 touches
1 conflict

0xf2f76ab3…623e

0x2a68ba…90c5

4 touches
1 conflict

0x00000000…0013

0x1b6862…e19c

4 touches
1 conflict

0x00000000…0000

0x5a52cc…1d7e

4 touches
1 conflict

0x00000000…0002

0x5a52cc…1d7e

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

45 conflicts on slot 0xfdc0fc0b8c…282b6d

← previous block·next block →recent activity