← previous blocknext block →recent activity

Analyzing

Block #74,259,952

21 transactions · 12 stateful · 2026-05-13 05:46:56 UTC

Parallelism

81/100

Blocked

42%

Avg conflicts / tx

0.43

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #74,259,952  ·  21 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

0x8fd83eb0…7205

0xd32edf…ff58

7 touches
6 conflicts

0x6fd9ae7c…e97d

0x1b6862…e19c

6 touches
3 conflicts

0x00000000…0015

0x1b6862…e19c

6 touches
3 conflicts

0x00000000…0013

0x1b6862…e19c

6 touches
3 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0xb9d2cf20…a668

0x34b655…2a6f

6 touches
3 conflicts

0xbbee74c2…567a

0x065c9d…c394

4 touches
1 conflict

0x7cee1be1…e770

0x34b655…2a6f

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

6 conflicts on slot 0x8fd83eb018…327205

← previous block·next block →recent activity