← previous blocknext block →recent activity

Analyzing

Block #74,763,856

40 transactions · 30 stateful · 2026-05-15 13:50:50 UTC

Parallelism

80/100

Blocked

57%

Avg conflicts / tx

1.25

Longest chain

8 deep

Execution timeline

did this block parallelize well?

view

block #74,763,856  ·  40 txs across 8 waves  ·  depth 8
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

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

0xed6a41d0…ba63

0xd32edf…ff58

15 touches
28 conflicts

0x00000000…0002

0xab3526…fa38

10 touches
10 conflicts

0x00000000…0013

0x1b6862…e19c

8 touches
6 conflicts

0x00000000…0015

0x1b6862…e19c

8 touches
6 conflicts

0x00000000…001a

0x1b6862…e19c

8 touches
6 conflicts

0x00000000…002a

0x1b6862…e19c

8 touches
6 conflicts

0xba5743c7…21c1

0x1b6862…e19c

8 touches
6 conflicts

0xd9f18d9a…141d

0x1b6862…e19c

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

28 conflicts on slot 0xed6a41d05f…8fba63

← previous block·next block →recent activity