← previous blocknext block →recent activity

Analyzing

Block #74,920,262

24 transactions · 11 stateful · 2026-05-16 07:14:31 UTC

Parallelism

88/100

Blocked

27%

Avg conflicts / tx

0.17

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #74,920,262  ·  24 txs across 3 waves  ·  depth 3
parallel ↔ serial

wave w0

wave w1

wave w2

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

0x332fdebd…eb6e

0xd32edf…ff58

5 touches
3 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

4 touches
1 conflict

0x0b000000…0002

0x000000…1000

2 touches
0 conflicts

0x5d5b9f2a…4c6d

0x065c9d…c394

2 touches
0 conflicts

0x01e7b865…6e6d

0x188d58…ea8e

2 touches
0 conflicts

0x01e7b865…6e6e

0x188d58…ea8e

2 touches
0 conflicts

0x00000000…0012

0x1b6862…e19c

2 touches
0 conflicts

0x00000000…0013

0x1b6862…e19c

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

3 conflicts on slot 0x332fdebde4…dceb6e

← previous block·next block →recent activity