← previous blocknext block →recent activity

Analyzing

Block #74,331,227

36 transactions · 26 stateful · 2026-05-13 13:41:04 UTC

Parallelism

83/100

Blocked

46%

Avg conflicts / tx

0.61

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #74,331,227  ·  36 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

0x60f7fbaf…bd58

0x34b655…2a6f

10 touches
10 conflicts

0x4381471a…9ac1

0x34b655…2a6f

8 touches
6 conflicts

0x664bf99e…0a8c

0x34b655…2a6f

8 touches
6 conflicts

0xbfca3cd0…5023

0x34b655…2a6f

8 touches
6 conflicts

0xeb0915f1…c150

0x34b655…2a6f

8 touches
6 conflicts

0xfdbd6ee7…1a22

0x34b655…2a6f

8 touches
6 conflicts

0xafd59af5…5257

0xc8689a…ee79

8 touches
6 conflicts

0x15c9b5bf…f732

0x34b655…2a6f

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

10 conflicts on slot 0x60f7fbaf90…97bd58

← previous block·next block →recent activity