← previous blocknext block →recent activity

Analyzing

Block #74,722,195

35 transactions · 28 stateful · 2026-05-15 09:12:10 UTC

Parallelism

77/100

Blocked

61%

Avg conflicts / tx

0.91

Longest chain

8 deep

Execution timeline

did this block parallelize well?

view

block #74,722,195  ·  35 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

0x60f7fbaf…bd58

0x34b655…2a6f

12 touches
15 conflicts

0x5675c293…17d9

0x34b655…2a6f

6 touches
3 conflicts

0x62d080e9…4a7c

0x34b655…2a6f

6 touches
3 conflicts

0x00000000…0019

0x1b6862…e19c

6 touches
3 conflicts

0xcb45d9d6…cb81

0x1b6862…e19c

6 touches
3 conflicts

0x17606ba6…1b6e

0x754704…b603

6 touches
3 conflicts

0xd9f18d9a…141d

0x1b6862…e19c

6 touches
3 conflicts

0x41755291…977f

0x065c9d…c394

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

15 conflicts on slot 0x60f7fbaf90…97bd58

← previous block·next block →recent activity