← previous blocknext block →recent activity

Analyzing

Block #74,456,162

46 transactions · 29 stateful · 2026-05-14 03:32:34 UTC

Parallelism

76/100

Blocked

66%

Avg conflicts / tx

1.63

Longest chain

11 deep

Execution timeline

did this block parallelize well?

view

block #74,456,162  ·  46 txs across 11 waves  ·  depth 11
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

wave w9

wave w10

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

0xd023fb56…d4f5

0xd32edf…ff58

21 touches
55 conflicts

0xf3981be5…2c47

0x34b655…2a6f

12 touches
15 conflicts

0xea02471d…1542

0x34b655…2a6f

10 touches
10 conflicts

0x00000000…0015

0x1b6862…e19c

6 touches
3 conflicts

0x00000000…001c

0x1b6862…e19c

6 touches
3 conflicts

0x00000000…002c

0x1b6862…e19c

6 touches
3 conflicts

0xd53220ed…4738

0x1b6862…e19c

6 touches
3 conflicts

0xd9f18d9a…141d

0x1b6862…e19c

6 touches
3 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

55 conflicts on slot 0xd023fb56c0…e5d4f5

← previous block·next block →recent activity