← previous blocknext block →recent activity

Analyzing

Block #74,331,809

35 transactions · 18 stateful · 2026-05-13 13:44:55 UTC

Parallelism

69/100

Blocked

61%

Avg conflicts / tx

1.6

Longest chain

11 deep

Execution timeline

did this block parallelize well?

view

block #74,331,809  ·  35 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

0xf07923e2…37e0

0xd32edf…ff58

21 touches
55 conflicts

0xf4381dd7…e66b

0x350035…7777

4 touches
1 conflict

0xe0b1916b…7af9

0x754704…b603

4 touches
1 conflict

0x00000000…0000

0xd215a9…b772

4 touches
1 conflict

0x00000000…0002

0xd215a9…b772

4 touches
1 conflict

0x00000000…0003

0xd215a9…b772

4 touches
1 conflict

0xc439a6eb…c510

0x188d58…ea8e

2 touches
0 conflicts

0xc439a6eb…c512

0x188d58…ea8e

2 touches
0 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 0xf07923e2b7…9d37e0

← previous block·next block →recent activity