← previous blocknext block →recent activity

Analyzing

Block #74,331,780

47 transactions · 29 stateful · 2026-05-13 13:44:43 UTC

Parallelism

83/100

Blocked

59%

Avg conflicts / tx

0.89

Longest chain

8 deep

Execution timeline

did this block parallelize well?

view

block #74,331,780  ·  47 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

0x631a3693…d04d

0xd32edf…ff58

13 touches
21 conflicts

0x17606ba6…1b6e

0x754704…b603

10 touches
10 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

8 touches
6 conflicts

0x692a4122…76b8

0x350035…7777

6 touches
3 conflicts

0x00000000…0003

0x116e7d…d8f1

6 touches
3 conflicts

0xb7143610…adc4

0x3bd359…433a

6 touches
3 conflicts

0x00000000…0000

0x116e7d…d8f1

6 touches
3 conflicts

0x00000000…0002

0x116e7d…d8f1

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

21 conflicts on slot 0x631a369324…5bd04d

← previous block·next block →recent activity