← previous blocknext block →recent activity

Analyzing

Block #74,891,084

21 transactions · 16 stateful · 2026-05-16 03:59:55 UTC

Parallelism

76/100

Blocked

44%

Avg conflicts / tx

0.52

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #74,891,084  ·  21 txs across 5 waves  ·  depth 5
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

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

0xfe2bac2b…2cec

0x065c9d…c394

8 touches
6 conflicts

0x00000000…003d

0x065c9d…c394

6 touches
3 conflicts

0xf3d7a307…4d63

0x065c9d…c394

6 touches
3 conflicts

0x18980d2c…017b

0xd32edf…ff58

5 touches
3 conflicts

0x4aa4f53b…89a0

0x188d58…ea8e

4 touches
1 conflict

0x00000000…0012

0x1b6862…e19c

4 touches
1 conflict

0x00000000…0013

0x1b6862…e19c

4 touches
1 conflict

0x33018431…8f5c

0x188d58…ea8e

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: 0x065c9d28…a9c394

6 conflicts on slot 0xfe2bac2b2f…482cec

← previous block·next block →recent activity