← previous blocknext block →recent activity

Analyzing

Block #74,458,659

28 transactions · 26 stateful · 2026-05-14 03:49:11 UTC

Parallelism

71/100

Blocked

73%

Avg conflicts / tx

2.5

Longest chain

8 deep

Execution timeline

did this block parallelize well?

view

block #74,458,659  ·  28 txs across 8 waves  ·  depth 8
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

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

0xd98b3c10…67b8

0x34b655…2a6f

16 touches
28 conflicts

0x385e1e53…1332

0xd32edf…ff58

15 touches
28 conflicts

0x1c389468…6b0e

0x34b655…2a6f

12 touches
15 conflicts

0x17606ba6…1b6e

0x754704…b603

8 touches
6 conflicts

0x00000000…002c

0x1b6862…e19c

6 touches
3 conflicts

0xac79a0c7…be13

0x1b6862…e19c

6 touches
3 conflicts

0xd9f18d9a…141d

0x1b6862…e19c

6 touches
3 conflicts

0x7cee1be1…e770

0x34b655…2a6f

6 touches
3 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: 0x34b6552d…112a6f

28 conflicts on slot 0xd98b3c102b…ca67b8

← previous block·next block →recent activity