← previous blocknext block →recent activity

Analyzing

Block #74,433,118

29 transactions · 19 stateful · 2026-05-14 00:59:11 UTC

Parallelism

72/100

Blocked

47%

Avg conflicts / tx

1.07

Longest chain

8 deep

Execution timeline

did this block parallelize well?

view

block #74,433,118  ·  29 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

0x17606ba6…1b6e

0x754704…b603

12 touches
15 conflicts

0xec41f0b6…baf9

0xd32edf…ff58

11 touches
15 conflicts

0x93afca4c…b47b

0x1b6862…e19c

8 touches
6 conflicts

0x00000000…0012

0x1b6862…e19c

8 touches
6 conflicts

0x00000000…0013

0x1b6862…e19c

8 touches
6 conflicts

0x00000000…0015

0x1b6862…e19c

8 touches
6 conflicts

0x00000000…002b

0x1b6862…e19c

8 touches
6 conflicts

0x00000000…001b

0x1b6862…e19c

8 touches
6 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: 0x754704bc…afb603

15 conflicts on slot 0x17606ba612…ea1b6e

← previous block·next block →recent activity