← previous blocknext block →recent activity

Analyzing

Block #74,762,117

18 transactions · 13 stateful · 2026-05-15 13:39:14 UTC

Parallelism

78/100

Blocked

38%

Avg conflicts / tx

0.33

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #74,762,117  ·  18 txs across 4 waves  ·  depth 4
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

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

0xf89adb9f…f2a7

0xd32edf…ff58

5 touches
3 conflicts

0xf2f76ab3…623e

0x2a68ba…90c5

4 touches
1 conflict

0xd98b3c10…67b8

0x34b655…2a6f

4 touches
1 conflict

0x7c403af1…31b1

0x3bd359…433a

4 touches
1 conflict

0xba5743c7…21c1

0x1b6862…e19c

4 touches
1 conflict

0x00000000…0000

0xd5b70d…615b

4 touches
1 conflict

0x00000000…0003

0xd5b70d…615b

4 touches
1 conflict

0x00000000…0004

0xd5b70d…615b

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

3 conflicts on slot 0xf89adb9f21…90f2a7

← previous block·next block →recent activity