← previous blocknext block →recent activity

Analyzing

Block #74,638,194

14 transactions · 12 stateful · 2026-05-14 23:51:58 UTC

Parallelism

71/100

Blocked

42%

Avg conflicts / tx

0.57

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #74,638,194  ·  14 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

0xe2a70f38…58e6

0xd32edf…ff58

7 touches
6 conflicts

0xa9988419…9f45

0x34b655…2a6f

4 touches
1 conflict

0x00000000…0004

0x5afd3e…7620

4 touches
1 conflict

0x5d82c9b5…004c

0x3bd359…433a

4 touches
1 conflict

0xef7bbb1c…9bf8

0x065c9d…c394

2 touches
0 conflicts

0x00000000…0012

0x1b6862…e19c

2 touches
0 conflicts

0x00000000…0013

0x1b6862…e19c

2 touches
0 conflicts

0x00000000…0015

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

6 conflicts on slot 0xe2a70f380e…2b58e6

← previous block·next block →recent activity