← previous blocknext block →recent activity

Analyzing

Block #74,413,635

39 transactions · 26 stateful · 2026-05-13 22:49:28 UTC

Parallelism

69/100

Blocked

54%

Avg conflicts / tx

1.18

Longest chain

12 deep

Execution timeline

did this block parallelize well?

view

block #74,413,635  ·  39 txs across 12 waves  ·  depth 12
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

wave w9

wave w10

wave w11

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

0x37043742…7d39

0xd32edf…ff58

17 touches
36 conflicts

0xd025d7d7…f05a

0x3bd359…433a

6 touches
3 conflicts

0x12309510…0ac2

0x000000…012a

6 touches
3 conflicts

0x2bbc0cfb…c2be

0x1b6862…e19c

6 touches
3 conflicts

0x00000000…0013

0x1b6862…e19c

6 touches
3 conflicts

0x00000000…0015

0x1b6862…e19c

6 touches
3 conflicts

0x00000000…002b

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

36 conflicts on slot 0x3704374261…477d39

← previous block·next block →recent activity