← previous blocknext block →recent activity

Analyzing

Block #74,190,702

17 transactions · 12 stateful · 2026-05-12 22:06:29 UTC

Parallelism

65/100

Blocked

58%

Avg conflicts / tx

1.06

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #74,190,702  ·  17 txs across 6 waves  ·  depth 6
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

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

0xe7954f22…cf2b

0xd32edf…ff58

11 touches
15 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0x15c9b5bf…f732

0x34b655…2a6f

4 touches
1 conflict

0x8e66da19…66b6

0x065c9d…c394

2 touches
0 conflicts

0xe842b34b…fc1d

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

15 conflicts on slot 0xe7954f225f…33cf2b

← previous block·next block →recent activity